It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Duplicate - Reject or Resolved


When we have an issue that is dup we want to move it to next status.
There are two option:
1. Resolved - resolution duplicate.
2. Reject - resolution duplicate.
In both cases the developer will solve the issue with origin issue.

We have a hot debate what is the right status, and I would like hear how it is done in other places.

1 comment


we link the issues with "Duplicates" & sync the status from the parent issue to the duplicate. Sometime it turns our later that an issue is not a duplicate as it was on first glance. Then you can still split them up again. Sometimes each of the issues contains information that is needed to solve the problem.

You can also configure a board to not display issues that contain a "Duplicate" link.



We also link the issues but not sync.
Does the sync happen automatically?

No, we use a post function & ScriptRunner.




Log in or Sign up to comment
Community showcase
Posted in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

3,718 views 11 5
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you