Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,415,130
Community Members
 
Community Events
170
Community Groups

Duplicate - Reject or Resolved

Hi

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

Hm,

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.

Best

JP

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

No, we use a post function & ScriptRunner.

Best

JP

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events