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,462,992
Community Members
 
Community Events
176
Community Groups

Automatically set statuses of issues with a linked type of duplicate to always match

I am trying to find a solution for an issue we have. 

Our issue: 

We often get duplicate Bugs filed. We choose a primary bug to track the actual work against and to date, we have been closing out the duplicates as "resolved - duplicate" immediately when they are identified as a duplicate. We don't like this solution because it gives a false impression that the issue reported in the bug is resolved, when in reality, its not resolved until the issue it duplicated is resolved and without a little bit of digging through JIRA links, that is not readily apparent. Here is a small example that can help better explain what I am hoping someone has a solution for: 

Issue BUG-1 is filed on Monday 

Issue BUG-2 is filed on Tuesday 

After reviewing BUG-2, its determined to be a duplicate of BUG-1

We want to have the assignee, status, and resolution of BUG-2 update automatically to match what is set in BUG-1 every time those fields change. 

 

1 answer

0 votes

Hey Alexandria, I'm trying to understand the impact of this since from my point of view linking and closing could be just fine.

What are some examples of situations that occured when you had linked & closed a "BUG-2" in the past?

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events