Using "Release" as the "feature" level

Kevin Dickson

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: 

1. Create a release called <My Feature> with release start/end dates
2. Group all stories within that release so that we know what feature they roll up into.

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.

Humashankar VJ

Hi @Kevin Dickson 

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.

• Benefits of this method include easy grouping and reporting, timeline management, simplicity, and visibility across Jira dashboards and filters. However, potential issues arise from semantic clarity, impact on long-term planning, limited hierarchical depth, and capacity management.

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."

• Use releases as features if your team is on board and there are no immediate DevOps integration plans.
• Consider Jira Premium for custom hierarchy levels or use Components as a temporary solution.

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