I am exploring the best pratices to use epic and fix version.

Sanchit Korgaonkar February 21, 2024

Currently we are using epic as a large container for product feature-holding stories.  

Examples of some of my Epics: Feature 1 , Feature 2. It is never ending and explains the product structure. Though we are not able to use it very effectively. 


Same time we are using fix version for the projects - for example - Feature 1 has 10 stories but if we are working on its phase 1 and only 5 stories are going to be delivered then we mark all those five stories as part of fix version with name feature 1 phase 1. 

Want to understand the best practices and easy-to-use method? 

Option I am exploring is 

Epic as project and having concrete end time. 
Fix version as every release containing all the features that would release in that month

1 answer

1 accepted

0 votes
Answer accepted
Marketplace Partner
Marketplace Partners provide apps and integrations available on the Atlassian Marketplace that extend the power of Atlassian products.
February 21, 2024

Hi @Sanchit Korgaonkar 

It's Mary from Planyway for Jira: workload, roadmapping, time tracking


Here are some best practices and considerations based on your current situation and the option you're exploring:

1. Rethinking Epics as Projects with a Concrete End Time

Using epics as large containers for product features is a standard practice. However, treating epics as projects with concrete end times can help in a few ways:

  • Improved Focus and Clarity: By defining a clear scope and timeline for what is essentially a mini-project, your team can focus better on the immediate goals.
  • Better Tracking and Reporting: This approach allows for more straightforward progress tracking against specific objectives and deadlines.
  • Enhanced Flexibility: As priorities shift, you can more easily adjust the scope of work within an epic/project without losing sight of the larger product roadmap.

2. Using Fix Versions for Releases

Leveraging fix versions to represent releases is a great way to track what features and stories are going out in each release cycle.

  • Clear Release Planning: This method allows for clear and organized planning of what is being released and when, facilitating better communication with stakeholders.
  • Enhanced Visibility: It provides all team members with visibility into the progress towards upcoming releases and what features are included.
  • Simplifies Reporting: Reporting on progress, issues resolved, and features delivered in each version becomes more straightforward.

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events