Version 1.0 has a bug called FT-1 "Photo upload bug": When a user attempts to upload a profile picture
the app crashes. This issue is then assigned, fixed, tested and closed with no further problems on Version 1.1.
Several versions later (Keep in mind this bug doesn't appear in version 1.1 - version 3.1 and successfully
passes all QA tests), version 3.2, we identify a bug that results in the same crash as a result of a user attempting to upload a profile picture.
Should this re open the FT-1 "Photo upload bug" which was tested and closed, or should this
be treated as a new bug FT-2 "Photo upload bug", in order to avoid the assumption that this
bug has been present throughout each version.
On the Atlassian Connect team we always raise a new issue if an old bug has been released in a previous version. Our reason is that we never want the same issue to be released twice. To accomplish this easily we either:
I hope this helps.
Hi Robert. Just to clarify;
"...we always raise a new issue if an old bug has been released.."
Working on the assumption that you fixed, tested and resolved the original bug in version 1.1.
You now move on with your wonderful development life, and then when you notice a new
bug that results in the same undesirable result (FT-1: App crash from photo upload), you just create a new bug issue (FT-2.....) FT-1 vs FT-2 for version 3.2?
Thanks, hope that is clear?
I agree with Robert's answer (+1'ed!).
Provided that a symptom may be produced by different root causes, I'd say it would be better not to assume that it is the very same bug, before having researched on it:
What would it happen if, after having reopened the old issue and worked on it for several days, you notice that it is produced by a completely different cause, but that it just had a quite similar symptom?
So, in my opinion, creating a new bug with the same description is better.
I would suggest linking the new issue with the old one through an issue link with a 'relate to' relationship, initially.
If, after having worked on the issue, it is determined that both issues have exactly the same symptom and root cause, then you can change the relationship to 'duplicate'.
Besides, a new issue is easier to track for reporting purposes and populating gadgets than a reopened one.
Hi Community! The Jira Service Desk marketing team is looking for customers who have successfully switched from Zendesk to Jira Service Desk! We’d love to hear your thoughts on the pros and ...
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