Dear @Ankuskum
interesting requirement. Why do you need to do this?
Anyhow, by using normal issue operations, you can't avoid this. It's the design of Jira to log all changes into the history and update the updatedDate.
But you can alter the DB directly. Not really recommended, because you could mess up everything. Alternatively, you can export your entire Jira to XML backup file, modify the status of your epics and re-import (restore). That's saver than direct DB, because Jira does a validation on import.
If you plan do to this, make a dry-run in a non-productive environment, first.
So long
Thomas
Hi @Ankuskum
Yes, and...to the question from Thomas: what problem are you trying to solve by doing this?
If such unlogged edits were generally possible in Jira, it would break the history of issues, making the log of changes worthless. You could never rely upon it when you needed it.
I wonder if you have a different need and saw this as a possible solution. For example, is there some prior issue change that you want to have preserved as the last update date/time?
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.