I created a new release (version) in our project in Jira. I added the release on the user story issues in the Fix Version field, so that I can see those issues in the release. During test a new bug was found. A new bug issue was created and associated with the User Story using the Is Caused by link. I put the release in the Affects Version field on the bug record. I want to be able to see from the release that this bug was found in that release, but in the release is only showing the user story issue.
Am I using the Affect Versions and Fix Version fields correctly?
How can I see bugs that are found in a release form the release screen? I want to know if a release contain bugs before it goes to production.
Thanks!
Michelle
Hi, Michelle
To give you some context first, if if you Affects versions as 1.0 in your issues, for example, generally, it is used for versions of your software which is being affected by a Bug.
So, if you set 1.0 in the field Affects versions, it means that this version is the one with the problem.
The Fix Version/s is used for versions of your software where you fixed the Bug.
So if you search with a JQL like fixVersion = 1.0 field to search for the version's issues, it will return only 'fixed' issues, while searching for affectedVersion = 1.0 will return the affected issues.
Let me know if this makes sense to you and helps to better understand when you should user Affect Versions/Fix Versions fields. :)
Gabi
Thanks @Gabriele Franck. So it sounds like I can make a filter for that, but from the release record it will only show issues where fix version is filled in. Is that correct?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That's correct, Michelle! :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.