Hello everyone,
I have added a custom field which links an issue to a specific release, which will help my team keep issues in the backlog categorized by future release. I have labeled the field 'Linked Release.'
The 'Fix Release/s' and 'Affects Version/s:' field are current being used for the appropriate purposes.
The issue that I am having with the 'Linked Release' pick list, is that when I associate an issue with a release and then go to --> Releases..the associated issue(s) are not showing as actually being linked to the particular release.
Instead, the release shows 'No Issues.'
Is there a way to tell Jira that this issue is associated with this release?
Please help as this is causing me major anxiety!
The Releases issue list is based on Fix Version/s - creating a custom field won't make the issue show up on that list.
Why do you need a different release custom field from Fix Version/s?
Hi Derek,
Thank you for the response, maybe I am overly anal about the organization of our data but, the Fix/ Version field is currently being used specifically for bug fixes that pertain to a specific version. As we know, all issues are not bug fixes and for new features this field will help me plan a new release by linking the issue (new feature) to a future release.
Does this make sense?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You are thinking too narrowly. This field is used to associate the Issue with the Release. Don't think about it as Bug Fixes but as the collection of issues that are associated with this release.
You should Affects Version/s to identify which Releases are affected by the bug. Since new functionality doesn't affect existing releases, this field will be empty. Use Fix Version/s to indicate which version/s will deliver the issue. This would be the list of bugs and new features that are part of the future release
You can differentiate between bugs and new functionality by Issue Type.
Does this help?
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.