Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

In this Discussion

osTicket v1.10 (stable) and Maintenance Release v1.9.15 are now available! Go get it now

Dead or alive? - Continued...

2»

Comments

  • I too would really love to see an individual client login that I can give and revoke access.
  • More on client logins...

    I have had osTicket fully deployed now since the first of March. Prior to deployment, I had fully reviewed no fewer than 8 open source support ticket systems while performing test installs of around half. osTicket was the only one that was easy to understand and configure on my end, and, most importantly extremely easy to navigate from a customer perspective. Kudos to all the developers.

    The application, as is, performs flawlessly as it is currently designed. I have no complaints on the existing 1.6 version. However, I do have one suggestion pertaining to client logins to make it easier on the customer/client side for them to be able to manage their support tickets. And, there is a very simple solution.

    Currently all tickets are grouped by user and e-mail--quite nice, as access to one ticket provides access to all tickets that a user@emailaddress has opened. However, there is currently no way to effectively provide access to all tickets at a given client site to a client liason at the site. I did try to do this by creating a group called " Liasons." I have Departments created for each company, and the "Group" option allows me to restrict access to tickets by these departments. However, there is one simple element missing that would allow me to be able to create a "client" user with access to all tickets at their site as follows:

    There are now five restriction options under the "Group" settings:

    Can Create Tickets Yes/No
    Can Edit Tickets Yes/No
    Can Close Tickets Yes/No
    Can Transfer Tickets Yes/No
    Can Delete Tickets Yes/No
    Can Ban Emails Yes/No
    Can Manage Premade Yes/No

    With the addition of one other option here:

    Can See Internal Comments Yes/No

    One would then be able to create a master client-user login, giving them access to all their site tickets by department, without giving them access to one's own proprietary information that one does not want a customer/client to see.

    I believe that this would provide a whole new level of add'l functionality with a very simple update, probably for add'l purposes, other than what I've outlined here, as well.

    Thanks!
    Tim
  • Add'l on the immediate preceding post on client logins

    Actually, you would probably want to set that option to be:

    Can See/Post Internal Comments Yes/No

    Or some permutation of the above, as you would create confusion if they could post internal comments that they cannot see. The above should cover the basics though at first.

    If I'm missing something here, I'm sure someone will think of it.
  • Great news!!!

    I'm diving into the new code right now, loving GitHub development tree... I think this way will be easier to help the project coding new features ;)

    P.D.: anyone trying to make it multilang? :p

    P.D.2: I know, I have two pending things for 1.6 and I am the worst :(
  • anavmon;26789 said:
    Great news!!!

    I'm diving into the new code right now, loving GitHub development tree... I think this way will be easier to help the project coding new features ;)

    P.D.: anyone trying to make it multilang? :p

    P.D.2: I know, I have two pending things for 1.6 and I am the worst :(
    I am looking at the code for 1.7 and, although I'm quite a noob, I find it quite a great learning tool....

    So I have been considering exploring the use of gettext and poedit.... Perhaps it will speed up the translation of files, make the changes stick to general release and ease the burden of the real programmers, as they won't have to think too much about the translations.

    Anybody else have this running? I don't want to step on toes and I certainly don't want to piss off the programmers who need to make changes on git like yesterday...

    My kudos and congrats to everybody by the way... As I learn I might have too many questions, far too many.... or I might just faint when I realize I am not even knowledgeable enough to be even just a tiny bit dangerous... :D
  • When its final version 1.7 for production use is expected to release?
    I want to upgrade my osticket soon... Please reply.
    Thanks.
  • anavmon;26789 said:
    Great news!!!

    I'm diving into the new code right now, loving GitHub development tree... I think this way will be easier to help the project coding new features ;)

    P.D.: anyone trying to make it multilang? :p

    P.D.2: I know, I have two pending things for 1.6 and I am the worst :(
    I'm also looking for an opportunity localize product to Cyrillic, tell me how true test is done?
  • Running 1.7 DRP3. Upgraded from DRP2. The upgrade failed though. First it tried to use the database table ost_ticket_thread which didn't exist. After running it again, I got forward but complained because the sub argument returned more than 1 line, which I was able to resolve by deleting the staff members. Since this is just a test thing for us now there was no data in the databases of anything of value, so I just blew it away and started it fresh with DRP3.
  • I get this error if I select the default email template.

    -------------

    [SELECT tpl.*,count(dept.tpl_id) as depts FROM ost_email_template tpl LEF= T JOIN ost_department dept USING(tpl_id) WHERE tpl_id=1]



    Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is = illegal if there is no GROUP BY clause
  • davidlee;27040 said:
    I get this error if I select the default email template.

    -------------

    [SELECT tpl.*,count(dept.tpl_id) as depts FROM ost_email_template tpl LEF= T JOIN ost_department dept USING(tpl_id) WHERE tpl_id=1]



    Mixing of GROUP columns (MIN(),MAX(),COUNT(),...) with no GROUP columns is = illegal if there is no GROUP BY clause
    We'll look into the issue.

    PS. Everyone helping with testing - please log issues in GitHub
  • DB error with 1.7 DR3

    Hi,

    I am getting the below mentioned DB Error when I create a ticket.

    DB Error #1054

    [SELECT m.staff_id FROM ost7_staff m WHERE m.dept_id=1 AND s.staff_id IS NOT NULL ORDER BY s.lastname, s.firstname]

    Unknown column 's.staff_id' in 'where clause'

    Kindly look into this and also let us know the date when the stable version of 1.7 will be available.
  • Cannot print Tickets

    Hi,

    When I open a ticket and to print the ticket when i click on the print ticket button, it doesn't print the ticket.

    kindly look into the same as well.
  • Shows all closed tickets

    Hi,

    When all the open tickets are closed then it shows all the closed tickets.

    It must show "query returned 0 results" instead of closed tickets as it creates confusion a lot of time. This was a drawback in the 1.6 version. Kindly rectify this in the 1.7 version release.
  • @leovipin1 Please log issues in GitHub.
  • So unfortunately there is still no new stable release?

    I don't dare to ask for an estimate, but any idea?

    David.
  • Secret way to speed development. *shhh*

    The more of us who use, test, and submit bug reports for the beta version, the faster it will come out.

    I'm launching a new help desk and figure that my users can handle a slightly fragile help desk system considering how much better it will be than what we have now. So long as 1.7 -mostly- works now, I'm starting off with it.

    -J
    DavidH;27226 said:
    So unfortunately there is still no new stable release?

    I don't dare to ask for an estimate, but any idea?

    David.
  • i want to use the export option which is there in ticket view screen in osTicket-1.7.. to osticket 1.6

    pl suggest :)
  • can any body guide on this pl..:(

    i want to use the export option which is there in ticket view screen in osTicket-1.7.. to osticket 1.6
  • Release date????????

    Any info about release date for public use? I am asking it twice please answer.
    Waiting for new version.
    Thanks.
  • https://github.com/osticket

    osTicket-1.7

    Last updated a month ago


    No comments... :(
  • Where is the tranlation module?

    I waiting for years.

    I installed 1.7. and...

    No stratategy for translations? :mad:
  • shitansh;27639 said:
    Any info about release date for public use? I am asking it twice please answer.
    Waiting for new version.
    Thanks.
    There is no release date at this time.
  • Sidon;28017 said:
    I waiting for years.

    I installed 1.7. and...

    No stratategy for translations? :mad:
    I'm not sure why your "mad", you installed a preview developer release.
    It is clearly stated this is not intended for stable or production machines.
    I recommend that you use the current version 1.6ST until 1.7ST is released.
  • Looking forward

    I'm definitely looking forward to the next version of osT and a tighter release cycle.

    I'm also interested in the timeframe for the next release because I am working with some developers with the hopes of taking osT to the next level in terms of integration with current CMS engines, namely Wordpress...

    I checked out the zingiri plugin, and it really doesn't do this software justice.

    I hope that your team is able to find the time to finalize the 1.7 release because the community appears to be very anxious to get started working with it.

    Has a more definitive set of features that will be included in this release been made available yet>?

    Thanks!
    Troy
  • Hi there, I'd like to start a new thread to start discussions about my v1.7 enhancements at github (https://github.com/soif/osTicket-1.7) .

    But I can't figure where. :confused:

    I tried to post a new thread in Announcements Discussion, but it is moderated. :( And all others forums are related to versions 1,6 or oldest versions. :eek:

    Any advice on where to post, would be appreciated. :rolleyes:

    Thank you
  • I think that Peter is the only one who can setup new areas in the forum. You should probably PM or email him about it. He may be unwilling to add 1.7 areas until there is a RC release to minimize confusion though.
    soif;28337 said:
    Hi there, I'd like to start a new thread to start discussions about my v1.7 enhancements at github (https://github.com/soif/osTicket-1.7) .

    But I can't figure where. :confused:

    I tried to post a new thread in Announcements Discussion, but it is moderated. :( And all others forums are related to versions 1,6 or oldest versions. :eek:

    Any advice on where to post, would be appreciated. :rolleyes:

    Thank you
This discussion has been closed.