in the history of each ticket, if an agent change the help topic or the ticket status, the history only shows "ticket updated" but the previous state does not are reflects in the history!
we have same problem, with our system, previous status history is lost when status is update.
We've added edit events to the ticket thread in v1.10; however, after a quick test, I see that help topic changes are not logged yet.
but i talking about 1.8/1.9 releases.. that its used in my production environment
normally in 1.9.6 the history changes are put in thew title of the history entry, but the only case in that its not record its in change status and change help topic
(in 1.10 i noted that but stability are still a doubt)
+1
My system running at 1.9.6, is stable and we don't have plans for updgrade, if you could solve this problem it would be very helpfull.
@Rankgel The devs don't generally back port new features to old versions. The only way to get new features is to upgrade, or implement the changes yourself.
@ntozier do u said that a missing history its a new feature!!!!! its suppost to be that history register all activities and we noted dont doit in those cases (ticket change topic)
I repeat: "The devs don't generally back port new features to old versions. The only way to get new features is to upgrade, or implement the changes yourself."
i added a fact to u'r reply, with this link:
https://github.com/osTicket/osTicket-1.8/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+1.9.9
seems that an upgrade are not very safe in a production environment! right guys? what do u think @Rankgel or @infectormp ? i see a lof of bug and annoying in 1.9.9 and 1.10
@mckaygerhard too much emotion :)
1.10 - it's major update and this version have a lot very awaiting futures (for me) and this is still a preview release (not for production) so he canmust have a lot of bugs that we all try catch at our test environment.
1.9.9 - we start using this version 8 days ago in production, we migrate from spiceworks. When i made decision start using osTicket i know about some bugs and annoying things. This sad but we can live with this, this is not fatal. For me not very important log help topic changes. It is not possible to implement all from first try and not make any errors in the code.
I don't know about devs experience with other helpdesk software (my about 12 years) but in general they create a very good product with some exclusive features that i not saw in commercial product. osTicket have great potential for grow and development.
Personal for me osTicket have some features that i don't understand, one of this future i describe here https://github.com/osTicket/osTicket-1.8/issues/1798
i used osticket for a year ago, from 1.9.2 and up only to 1.9.5, and its great, but my data are huge, VERY HUGE and its importante for us.. so its not easy to me upgrade somethig that have less "details" (to not said bugs) to another that are more newer just for "new features"..
i discovered this issue and i guess that its helpfull that bring support to see history changes that are missing..
my dissapointing are that this its a missing thing that its suppost to be..
we all must say thank you to @greezybacon for his commit 14f6902 that fixes this problem :)
thanks @greezybacon , umm there's no plans to backported that to 1.9.X series? i cannot updated to 1.10 too many huge data (i'm too busy to make track of errors)
also the change status of the ticket does not track in the history! must i open a new ticket for that also?
i currently updated only the code and use alwasy same sql data (with reapir tables), and in some cases track of changes (so far more easy) on the code fixeds..
if i paid support of 1.10, i'll be in same condition when made 1.11?
and i not still close due the problem that i reported are in 1.9.9
@mckaygerhard the new thread eventing system will not be backported to v1.9.x
ok ok there's so changes, can u tell me what commits may i backport to 1.9.X i really need that, i can made a backport but the code of osticket are poorly documented !
@greezybacon in the name of the comcepts of opensouce and collaboration explainme a little more (due lack of documentation) the commits related tho this issue, i can made a single patch and show here how other can implement and benefict for running production environments!
_i cannot update production env to 1.10 due i can see obviously that 1.10 still have many issues!_
due i still use 1.9 series of osticket in production and i really need _this MISSING functionallity_
A YEAR WAS END; AND STILL 1.10 NOT STARTING TO MAKE OFICIAL RELEASE; ONLY RC RELEASE CANDIDATES....
and suppose to i must install 1.10 in my production system!?!?
and @greezybacon i stll waiting how to backport this feature commit to 1.9 brand!!
so then when coume out 1.10? yeah, osticket now its a primary system used in my job! oh men osticket gorw up so many and now i depend on it!
i made some contributions and still that contribnutions not yet included in 1.9.X like the open attachments in new window! in every download i mus change code pieces to tune .. and i not developer!
and @ntozier i'm not taking about new threat system, i'm taking about that a bug its present! history are not reflected! in ticket history in any 1.9 relesas
so then when coume out 1.10?
As you have been told many times in many threads, 1.10 will be released when it is ready to be released. I'm not sure what part of that you aren't getting.
do mean that this clarelly bug its not supported that was confirmed agains 1.9 release, but will be correctly only in 1.10 that will not come today?
I can confirm that changes to the help topic are properly logged in the events in the ticket thread in v1.10-rc.3
but v1.10 are not stable and not official released yet!
please gime a break! do u suggest me to put in production a stil not stable/property completed software?
i report this ITS A BUG IN v 1.9 that are not happened, v1.9.11 does not logged changes to help topic in history threat! please!
mckaygerhard is right, the bug is presente in stable release, i have v1.9.11 and does not logged changes to help topic, i try ti fix it but unsuccessfully. some help here would be good
Sorry. It's not a bug. Nothing breaks when you update the help topic. It's a feature request, and it's been implemented.