We are running JIRA version 7.3.7 and Service desk version 3.4.0
When an issue is transitioned from an issue type not requiring approval to an issue type requiring approval, the Approval History is lost.
Is this a known issue? Please let me know what additional information you need to help troubleshoot / resolve.
If you're going from an issue type that does not require approval to one that does, since the initial issue type doesn't require approval it wouldn't carry the history with it from my understanding.
You can check the database to see if the data is there. Here are the relevant tables:
AO_56464C_APPROVAL: Approval data (name, issueId/statusId it associated with) and Approval Requirement and its final decision.
AO_56464C_NOTIFICATIONRECORD: Record notifications send to each approver.
Thanks Branden, your answer makes perfect sense.
Actually Atlassian support also weighed in with some suggestions (related to your answer...)...
After a little digging, it came down to this. When the issue was transitioned to the target (approval needed) workflow, it was transitioned to a post approval status (if that makes sense...).
Basically it comes down to either
1) When the issue is moved to the new workflow, transition it to a status that still requires approval, or
2) Change the target workflow to allow transitioning back to approval being required from anywhere in the workflow.
I posed those options to the customer...
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs