Epic Status a catch circular dilemma

[Jeff Koors]

For some reason our setup of Epic Status has Planned below Done. (see image)

What is happening is that upon selecting "Mark as Done" from the Epics panel in the backlog planning view it changes the Epic Status to "Planned" thinking this is the final status step.  When going back into the Epic Jira ticket and manually changing this to "Done", the epic shows back up in the Jira Backlog Epics Planning panel.

I used a post function to set the Epic Status to "Done" when the status of the ticket was transitioned to "Done".  This does us no good when we go to remove it from the Epic panel in the backlog planning view by "Mark as Done" when this triggers it to transition yet again back to "Planned".

It doesn't help that the field is locked too.  If the field wasn't locked, I would just move Planned in between "To Do" and "In Progress" where it probably should be anyway.

Any help here would be greatly appreciated.

[Trudy Claspill]

I am interested to learn how you were able to modify the context for the Epic Status field originally to get those additional options for it. The options for the field out of the box are simply To Do and Done. Since the field is locked, you should not have been able to modify the context to add more values. Do you have some sort of plugin that modified the context while keeping the field locked?

[Jeff Koors]

Trudy,

That is a great question and one that would predate me.  I've just recently come to discover this issue.  

[Trudy Claspill]

A Jira Administrator could review the installed Apps on your instance and see if any are likely to have made a change to the Epic Status field.

The only other way I can think of that they might have been altered is perhaps through an import of data. I haven't actually tried it, and I don't plan to try it, but perhaps an import of issues was done that included the Epic Status field and through that import additional values got added as options on that field.

Given that the field is locked, I can't think of a way that you can modify it at this point. Have you tried contacting Atlassian Support?

[Jeff Koors]

I think the latter is the reason.  We migrated Target Process through bulk import where this may have been introduced, but you'd think it would block or prevent a change to anything that is locked.

We are now stuck with a situation where we cannot "Mark as Done", which creates ever-lasting clutter in the backlog Epic management view.  This also creates a situation where it prepopulates all epics when manually typing in an Epic link.

[Trudy Claspill]

I would recommend contacting Atlassian Support to get help on this.

If you were using Jira Server/Data Center, then you might be able to fix it by careful and direct updating of the database. But that is not accessible with the Cloud hosted product.