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!
This might work...
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! My name is Amir and I’m on the Jira Service Desk product marketing team at Atlassian. Our team would love to understand how you’re leveraging our ecosystem for Jira Service Desk. Wha...
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