Hi All,
I provided instructions for the Classic Project work-around - and a workaround for Simplified / Next-Gen - on another question. This might be useful to some of you.
If you have a larger instance there might be an option utilising a global automation rule as long as you have All-to-All transitions in your workflows. If this is your example, let me know :)
-----------------
Classic Projects:
The post-function work-around mentioned in this issue will work for Classic Projects.
To implement this:
- As a Jira Admin, go to Jira Settings > Issues > Workflows
- Locate the required workflow, and press Edit. Move to diagram view.
- Select the "create" transition (arrow from the circle to the first status)
- From the pop-up, select "Post Functions"
- Press "Add Post Function" - and select the function "Update Issue Field", then press Add
- Choose the field "Resolution", and the value "None" - then press Add
- Next, on the right-hand side use the arrow buttons to move the clear resolution post function above "Create the Issue originally"
- Press Publish to activate the updated workflow
^ This will clear the resolution at creation.
-----------------
If you are using a Next-Gen project - or a Classic Project with a Simplified Workflow - the above workaround is not an option.
Instead, you can achieve the same result using a loop transition automation rule.
-----------------
Loop Automation:
Looping back to the same status will remove the resolution.
What this means is the transition will be from the first status, back to the same status. It's cleanest to do this loop transition via Automation.
For the Automation Rule:
- As a Project Admin, go to Project Settings > Automation in Classic Projects - for Next-Gen, go to Project Settings > Apps > Project Automation
- Press the blue "Create Rule" button
- For the Trigger, use Issue Created
- Add a Condition, Related Issues Condition - set Related Issues as "Linked Issues", Link Types as "clones" and Condition as "are present"
- Add an Action, Transition Issue - set the Destination Status as either the same status or "Same status (loop)"
- Give the rule a name and publish it
A few notes on the above rule:
- The rule fires just after creation - so refresh your page to see the resolution disappear
- You can modify the condition if you prefer to check the Summary for "CLONE -" or similar
- You can set this as a Global Rule as a Jira Admin via Jira Settings > System > Automation Rules. Just remember there are execution limits on global rules per month - whilst project executions are virtually unlimited.
-------------
The second option does require some setup to automate what might be a temporary problem as it's a bug - but it's a workaround which works today for those projects which cannot utilise a "complex" workflow.
Ste
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.