Epic Status - what's workflow, when is this set, how's it used?

I understand that Greenhopper is the layer/plugin that implements Epics as JIRA issues. There's a column called Epic status, where can I find doc on it's semantics? When is the field set, what are the possible values, is it an automatic or manual field, and how does it compare with the underlying issue status field?

thanks

3 answers

1 accepted

3 votes
Renjith Pillai Community Champion Feb 04, 2013

Epic Status was introduced to understand what state the Epic is in. A dependency on the JIRA workflow was not feasible since the boards can span across projects and the Epic workflow can be different. So it just depends on this custom field to decide what the status is. If the value of the field is the last option in the list, the Epic is considered as done.

It's not an automatic field, you change the status of the Epic using the board itself.

https://confluence.atlassian.com/display/GH/Completing+an+Epic

https://confluence.atlassian.com/display/GH/GreenHopper+JIRA+Configuration#GreenHopperJIRAConfiguration-Customfields

Thanks for the quick comment! Understand about Epics that can span projects - of course... When I asked about Epic workflow, I was really asking about the Epic life cycle. I see in the Epic panel where I can mark an Epic as done, but what are the other values of the field and where do they get set?

Also, in your note you say:

"If the value of the field is the last option in the list, the Epic is considered as done."

not sure what list you're speaking of... perhaps you could clarify. thanks again!

Renjith Pillai Community Champion Feb 05, 2013

I meant that the custom field 'Epic Status' has three values by default

  • To Do
  • In Progress
  • Done

The last value in the list is used by GH to consider that it is actual done. When a new Epic is created it is in To Do state. There appears to be no automatic change from 'To Do' to 'In Progress' and it is just a manual change to 'In Progress' if you need to mark an Epic as in progress.

And marking as done is documented at https://confluence.atlassian.com/display/GH/Completing+an+Epic

Perfect! thanks for the clarification... My take-away: since there's no automatic changes to Epic Status, we need to change our internal practices (mark as in-progress, or done) if we want to use Epic status in a meaningful way...

Hi @Peter Dittman, @Kramarics Györg,

We use a post-function to update the value of the Epic Status field on transition. That is then used to help us calculate the cycle time of the Epics. And it is available on Cloud too.

This is detailed in Understanding the cycle time of epics in Jira.

Hope that helps.

Regards,
Nick Muldoon
Product Manager, Easy Agile

Hey there,

I have read the documentation that you have mentioned, and I tried the same way like Nicholas with the transiton, so I had the same ideas. My problem is that I can not find the "Mark as Done" option. I made a test project with getting started function and also there isn't this option on the epics. I have the edit permission and no more ideas. Does anyone have?

Thank you,

Gyuri

I've got it. The list of the epic status filed was empty. So I added the three statuses, and it works.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,815 views 11 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot