I am struggling on figuring out on how I can manage the following situation. Basically, one request is sent by our key user (by creating an Issue) and then they can follow the development and availability. But then, it is possible that many test users report different bugs and then create several bug Issues. I read about the auto linking feature but this is not really convenient. It is possible that the new feature will generate only one bug issue, which then can be tracked on the original New Feature Issue, but what if there are many Bug issues?
What would be your best practices/recommendations?
Thanks for your help,
I guess there are many ways to do this. But here is how I would want to handle it. New Features should be part of a release version.
When testers find bugs, they should be finding it in a particular release. I would use the Affects version and Fix versions fields to capture all the bugs found in a particular release.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs