Our old workflows set the Resolution status to 8. Is there a way to find what the old 4.2.3 values correspond to in version 5.2
Is there a table list for example Resolution value of 8 is now DELIVERED Status?
See below workflow transition Post Function
|All||Conditions (1)||Validators (0)||Post Functions (7)|
Only the user defined in the Lead Tech field will be allowed to perform this Workflow Action.
No input parameters checks will be done before this transition is executed.
The Resolution of the issue will be set to 8.
Assigns the issue to the user in the Lead Tech field automatically.
Set issue status to the linked status of the destination workflow step.
Add a comment to an issue if one is entered during a transition.
Update change history for an issue and store the issue in the database.
Re-index an issue to keep indexes in sync with the database.
Fire a Issue Assigned event that can be processed by the listeners.
This is a slightly confused question. You use the phrase "resolution status", which is unclear in general, but when used in a Jira context, is dreadful. Resolution has a specific meaning. Status has a specific meaning. They are separate, distinct things which don't have any solid direct technical relationship. You can quite easily set up a situation where an issue can have status 1,2,3,4 or 5, and while it's in any of those status, have a resolution of X, Y, Z or none.
However, there's an easy answer to the main part of your question
> what the old 4.2.3 values correspond to in version 5.2
The upgrade does not change the underlying IDs unless you're coming from a REALLY old version. Resolution 8 in version 3.8 will land you with Resolution 8 in version 5.1 (and yes, I've recently done an upgrade that does that!)
I can see your status and resolution in your posting, but I'm not actually sure that there is a question there. You don't need to think about mapping, the upgrade hasn't changed anything. But you probably do need to reread your list of status, and the list of resolutions, to see what they're doing.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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