nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Clone now appears to clone resolution

Rob_8e38cr

Hi everyone,

As of this morning cloning a resolved issue appears to create a resolved clone...

Checked the audit logs, and config and can't see that anything has changed... or find a cause...

Yesterday a clone of a resolved issue would create an unresolved issue (we use this mostly for repetitive deployment tasks etc.)

Today they are all being marked as resolved as soon as we clone them...

Any thoughts, is this a bug or is it working for everyone else and we have some config issue somewhere?

Accepted answers

All comments

Flídr Marcel

Same on our site, probably a bug.

Irma Francis

The same thing happening for ours.

The first five or six clones get created in the same manner as before (as unresolved), and I can see them in a project backlog. Any others after that are created as resolved clones.

Tested this twice - same behaviour.

Vanna Beepat

Same thing happening to our organization.

John Price_aiexq9

I'm going to file a case. This is definitely a new bug, encountered for me today. Also since most workflows only have Clear Resolution on a re-open type status, it's not easy to clean it up.

John Price_aiexq9

I filed this as a Priority 2 support item and will link the related bug here once I know they have one. To check how extensive it is, you can run this JQL:



linkType = clones AND statusCategory != Done AND resolution is not EMPTY AND Created > -1w

John Price_aiexq9

OK, Atlassian pointed me to the bug tracker item:

https://jira.atlassian.com/browse/JRACLOUD-75040

Highest priority and they are working on it. Please go vote / watch.

Ste Wright

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

Darryl Lee

We also filed a ticket regarding this issue, and I've already voted and am watching https://jira.atlassian.com/browse/JRACLOUD-75040.

Question while we wait: Any ideas on how to disable Cloning while this is broken?

You can do it on Server:
https://confluence.atlassian.com/jirakb/disable-clone-issue-in-jira-747836996.html

Would be nice if we had the option on Cloud. Especially when it's broken.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

clone