I had previously marked an Epic as Done, as I considered it complete. We were asked to add another Story which we did, but now I'm unable to return the Epic Status to TO DO. My research thru Atlassian Community tells me that this is a locked field. Is there a JQL statement I can run to return this to TO DO status?
It's taken me some time to get back to researching this. We considered modifying the transitions in the workflow, but since all of our projects are tied to an existing workflow it seemed a bit risky, as my research tells me you must COPY the existing workflow to make edits and then apply the copy as the new, active one. Just seemed overkill.
I did find that I was able to add the Epic Status field to our Epic edit screen. I was then able to change the status from Done to In Progress and that met my needs. It now shows in my Kanban under In Progress, which is really what I wanted (not To Do). Thank you both for your assistance, but I found Randy's answer was the one I could use to resolve my question.
"Epic Status" is indeed a locked down field, and generally not available for editing. My JIRA Admin and I figured out that by temporarily adding the "Epic Status" to the Epic's edit screen (which is an Admin only task, especially when the screen is shared amongst projects), a user with "Edit" permissions can then change the value.
We did that and then reverted the Edit Screen change to keep the ability set as Atlassian had configured. The OP had also figured this out, but I thought it would be useful to pull this out to an individual answer...
@Victoria Danner , check the workflow for Epic issue type on your project, and make sure there is a transition that allows you to move the issue from "Done" back to "To Do" status. If you are not able to do this, then I suggest reaching out to your resident Jira admin. You can find more documentation on workflows in the Atlassian documentation here: https://confluence.atlassian.com/adminjiracloud/working-with-workflows-776636540.html
Correct answers were given above but showing the pictures might help. You will need to be project Admin to add the Epic Status field so you can update it.
Got to Project settings
Choose Epic under Issue Types
Add the Epic Status field
Then go back to the Epic you want to change the status and change the Epic Status value.
It never ceases to perplex me that Epics effectively have two parallel status fields - this is not in keeping with the level of agility Jira affords elsewhere and indeed seems like poor design with no tangible benefit. Why have inconsistent behavior across issue types? Especially when adding Advanced Road-mapping hierarchy above Epic, Epic remains the only level which requires this additional complexity.
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