nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to work with versions of a feauture or epic?

Anders Timsjö

Hi,

Im wondering if someone has a good suggestion for how to work with features and versions of that feature.

Lets say I have a epic describing a feature "Create an account view for the user" containing a few stories.
When 2 out of 4 of the stories are done we decide to release the epic as a MVP to production.

However there are still stories that are not done that we want to introduce in a later stage. Should I close the epic and create a new one for the remaining stories? If not the epic can not be set to done before all development on that epic is completed.

Do you have any good suggestions?

Thanks!

Accepted answers

Thomas Schlegel

Hi @Anders Timsjö,

I think of epics as containers. They are long-running, big issues, which contains smaller issues, the stories.

In our company, it is not unusual to keep an epic open for a long time, a year or even longer. Epics are not released to production, but stories are.

All comments

Thomas Schlegel

Hi @Anders Timsjö,

I think of epics as containers. They are long-running, big issues, which contains smaller issues, the stories.

In our company, it is not unusual to keep an epic open for a long time, a year or even longer. Epics are not released to production, but stories are.

Anders Timsjö

Hi, @Thomas Schlegel,

Thanks for the reply.

Ok I think that helps.

But it seems like epics in the places I have worked with JIRA are always tightly associated to a feature or represent a feature. Maybe the projects where I have worked use epic to much as a feature description and not a container.

Thomas Schlegel

I see. If you use epics like some kind of a story, you should take care of closing the epic in your sprint also.

So maybe you should create epics like feature1-part1, feature1-part2, etc. and close them with your sprint release.

Anders Timsjö

Yeah I think that might be the best approach.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud