Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

JIRA Projects for Software Product Lifecycle


My team has recently taken responsibility for a software product.

v4.0 is in production.

And we have a KANBAN board to handle the backlog of field issues.

A new v4.1 release is being worked upon.


How does one model a product life cycle in JIRA?

I create a single project for the product? (this way I keep a single backlog for the entire product)

And use versions to capture different releases?

Epics to capture features? ( a large body of work)

Stories to capture functionality

Tasks & sub tasks to capture the actual measurable eng work.

Components to track work (issues) from various angles. Product component, feature, theme (security, I18N...)

Please help with your suggestions



2 answers

We use JIRA 7.10 server version.

Additional suggestions:

1. We place SP estimates at story-level (i.e. New Feature, Improvements, Defects, Tech Debt, Chores).

2. Sub-tasks are used only for work which can be done in parallel (and without SP estimates)

3. JIRA Component field is used for the different modules within our tool.

We are using our KANBAN project as you mentined.

It is better to have one backlog for the same product.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events