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
We use JIRA 7.10 server version.
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.
Deliver better and faster value to your customers with the Jira automation platform. Watch this Demo Den series below to learn how to use the new interface and set up automation rules to help your te...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events