You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.
Join groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
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.
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?
Atlassian's marketplace partners have had a very productive start to 2021! Since our last roundup, our developer community has added over 160 new cloud apps to the Atlassian Marketplace to help you...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.