Hi community,
I'm having difficulty getting our Jira administrator to create the "feature" level within our hierarchy.
So...
Has anyone ever used the "Release/Version" option in Jira to record the features?
Example:
Does anyone see any issues with doing it this way?
I know that tools like Bamboo would have an impact if releases were automated, but we don't use any automation tools currently for the DevOps cycle.
Using Jira's "Release/Version" feature to represent a "feature level" is a creative workaround when custom hierarchy levels aren't available. This approach involves creating a release for each feature, assigning start and end dates, and grouping stories under the relevant release by setting the Fix Version field.
Consider alternatives like Components, Advanced Roadmaps (Jira Premium), or labels and custom fields to represent features. If adopting this approach, ensure documentation and training clarify the redefined meaning of "release."
To learn more
Version and Release Management in Jira | Jira Guru
Hope this helps - Happy to help further!!
Thank you very much and have a great one!
Warm regards
Thank you so much for your suggestions, @Humashankar VJ .
That is my biggest issues; that the Jira admin does not want to add "Features" as a hierarchy level between Epics and Stories.
Jira Premium does allow to change the hierarchy, but the Jira admin is against this, so I think either features or components would be a good idea.
We don't currently have a reliance on devops automating the releases, so this is a good interim solution then ...until I can convince the Jira admin to change his views ;-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @DC1
Your understanding is right, leveraging releases or components provides an interim solution for feature management, allowing the team to move forward without requiring immediate changes to Jira's hierarchy.
Best Regards
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @DC1 / @Humashankar VJ
Using issue links can be another way to create your a hierarchy. However the challenge is that Jira does not recognize that as a parent/child relationship. And you would need a mktplace app to view/manage that hierarchy. If you would be interested to try out one, pls take a look at
The app shows your issue hierarchy in a tree view created through Issue Links. The Issues in the tree can be in multiple projects and the app will pull out each one of them and show you a structured hierarchy. You can also filter specific linked issues as per your requirement. As you can see in the screen grab below, we have created an issue type Initiative at the top level.
The app has multiple other features which are very useful in project tracking and management.
(Disclaimer: I work for RVS, the vendor for this app)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Rahul_RVS
Unfortunately we're using Jira DC and it doesn't look as if the Issue Hierarchy app supports this?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @DC1 ,
Thanks for your reply.
For data center we have another app Agile Tools. This app has all the features of Issue Hierarchy plus time in status and worklogs reports.
Do give it a try.
Thanks
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.