We often have the situation where to resolve an issue, we need to raise a related issue. For example in order to satisfiy the issue:
UNI-115 - "The asset ID should be displayed on the Fault Screen"
we have raised
UNI-116 - "The DAO routine for retrieving Faults needs to be extended to include asset ID".
When we produce release notes for the customer - using the inbuilt JIRA release notes template system - we would like to exclude UNI-116, as it is not relevant to the customer.
One solution I can see is to introduce a custom field marking the UNI-116 as 'internal' or 'do not display on customer release notes', and then amend the release notes templates for customer release notes to take this field into account.
Alternatively, can we raise sub-issues and exclude sub-issues on customer release notes? One disadvantage of this would be that we may want some sub-issues to be customer-visible.
Any advice or suggestions would be welcome!
James
I think the best answer is to use an 'internal' custom field.
This might work...
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.