View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0023195||mantisbt||bugtracker||public||2017-08-07 11:56||2020-05-11 11:33|
|Priority||normal||Severity||major||Reproducibility||have not tried|
|Summary||0023195: Clone Issue modifies notes modified date in history|
Hello, in our company we are using quite often the feature to clone issues including their notes. Now we always struggle with the fact that notes are added to the cloned issue, but their timestamps in issue history is destroyed, because all notes get last modified from the moment when the issue is cloned. This is an issue because sometimes the order of adding notes is relevant. Is this working as designed, or is there a possible tweak to keep history timestamps for cloned issues?
|Tags||No tags attached.|
I am not sure if it's designed, but that's the way it's implemented at the moment.
Cloning issues including notes looks always a bit strange, as the clone does not reflect the real workflow.
It is not enough to add the seconds based on the order and write them in the change references copied from the old ticket.
The reason is that the copied notes were written by other users before the new ticket was copied, cloned or so on.
The change history should include a note copied from ID-old and the author (copier) of the new ticket.
So everyone knows their way around.
The author and the date of entry of the note or attachment must not be lost.
If you copy an ID with Checkbox in view_all_bug_page.php - the timestamps are correct.
|2017-08-07 11:56||mxit||New Issue|
|2017-08-13 09:53||atrol||Note Added: 0057450|
|2019-05-24 16:37||atrol||Relationship added||related to 0025792|
|2020-04-28 06:06||mahindra||Note Added: 0063927|
|2020-04-28 06:06||mahindra||Note Edited: 0063927||View Revisions|
|2020-04-28 06:07||mahindra||Note Edited: 0063927||View Revisions|
|2020-04-28 06:08||mahindra||Note Edited: 0063927||View Revisions|
|2020-05-11 11:33||mahindra||Note Added: 0063970|