Resolution Status Jira 4.2.3 to 5.2

KP11
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 20, 2013

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

Transition: Delivered

You are viewing an active workflow. Create a draft workflow.

Transition View: Release Screen 1.0

Workflow Browser
Verified
Delivered (51)
Delivered
(Originating Steps) (Destination Step)

All Conditions (1) Validators (0) Post Functions (7)

Conditions

Only the user defined in the Lead Tech field will be allowed to perform this Workflow Action.

Validators

No input parameters checks will be done before this transition is executed.

Post Functions

The Resolution of the issue will be set to 8.
— THEN
Assigns the issue to the user in the Lead Tech field automatically.
— THEN
Set issue status to the linked status of the destination workflow step.
— THEN
Add a comment to an issue if one is entered during a transition.
— THEN
Update change history for an issue and store the issue in the database.
— THEN
Re-index an issue to keep indexes in sync with the database.
— THEN
Fire a Issue Assigned event that can be processed by the listeners.

1 answer

1 accepted

0 votes
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 20, 2013

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.

Suggest an answer

Log in or Sign up to answer