How to limit resolution field only to some transitions even though we have global(all) transition

[Prince Suresh Kumar]

Hi,

I have a global transition to a status Re-open to all statuses, and i want whenever the status is set to Re-open the Resolution field needs to setup to unresolved but the issue is that i want the resolution field to set to unresolved only when the transition is from cancelled/ code migrated status to Re-open status but i am using a global(all) transition to Re-open status.

Can anyone please help me resolve the issue, as i am able to set the resolution field to unresolved but it is applying to all transition to Re-open status but i want to limit it to one/ two status?

[Petter Gonçalves · Accepted solution]

Hello @Prince Suresh Kumar

Thank you for reaching out.

Per your description, I understand you are trying to clear the resolution of your issues to unresolved when moving them to Re-open, however, only when the previous status was cancelled/code migrated status. Is that correct?

Indeed, it is not possible to achieve what you need with a global transition in the Re-open status, so the best approach would be to delete the global transition and create a single transition from the statuses you need. A good practice would be to use only two incoming transitions to "re-open" from two statuses "Closed or canceled", using the resolution field to define the other outcomes (Done, invalid, ignored, etc).

Additionally, I would like to bring you with some concepts and questions to better understand your goal and confirm we are on the same page here:

As you can see in this documentation, the Resolution field is a special field and is used by your reports and system fields define your issues as resolved, working in a boolean way: Set and Not set, although you can add custom displaying values to "set".

That being said, this field should never be set if your issue is opened or reopened, so I believe your goal to clear the resolution ONLY when the issue is coming from a different status would not be a good practice and could cause some unexpected behavior in Jira reports or system fields.

Could you please give us more information on why you want to configure your workflow this way? Maybe I can suggest you a different option to achieve your need.

 Let us know if you have any questions.