Mantis 2.26.1 on Windows
I've always wondered this, but why does the Timeline log the events in the wrong order when closing a ticket with a comment? Since the timeline flows UP into infinity (with older events at the bottom and the newest events at the top) when you close out a ticket and add a comment, the Timeline shows the Close event first and then it shows the Comment event. I'd consider that a bug...unless there's some mysterious reason why the devs wanted it to be that way. Please enlighten me.
In the Timeline log why are events out of order?
Moderators: Developer, Contributor
Re: In the Timeline log why are events out of order?
Think this is because first the bug is updated and next the note is added. In principle they happen on the same time, just a few milli seconds are in between which is enough to explain the order.
The correct way would be to set a timestamp @ the beginning of the process and use that for all updates. Result wil be random order
also not desirable.
The correct way would be to set a timestamp @ the beginning of the process and use that for all updates. Result wil be random order
also not desirable.Re: In the Timeline log why are events out of order?
So why not check for note text and update that AND THEN call the routine to update the ticket status afterward? Seems to be pretty straightforward, but of course I haven't looked into the code because this is such a low priority. Just a bit annoying to tell users who ask that it was "just how they programmed it..."