Hi
After a project import in JIRA it seems like old transitions in history are corrupt because it says "removed status" -> "removed status" in the transition tab. If I look in the history tab I can see what the transitions were and the "from status ID" -> "to status ID". However the status ID's are old and not the same as the current status ID's of the same status. This completely corrupt some statistics and reports.
Is there a way of updating those entries in the database so they become valid again?
I will add some pictures to this question. Perhaps it will make it more clear.
Here are the Transitions where some are considered removed the 20th of August.
Removed status.png
Here is the history that show the IDn from 20th of August. The same status's now have different IDn and I can't figure out how to change the wrong history.
Removed status IDn.png
Well that will not alter the history of things. The problem seems to be that there are entries in history that say the issue was transitioned from Status X [10010] to Status Y [10011] for example. The identical Status X now has id [40312) and Status Y has [40313] and those show up perfectly fine in the history. If I assign the project to a new workflow it will not be valid for old entries.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Linus, Atlassian never recommends making changes to the database directly. If done, they would not support. But based on your scenario, try to import / create a new workflow and assign to to the project. This is much easier than updating the databse. Regards, Sateesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.