Our "Epic Status" field configuration has somehow been modified and breaks stuff. How can I revert?

[Orrin Ward]

Recently some people in my team found that their Epic panels in their backlog views were filled with all their Epics, including old ones which were removed by "Mark as Done".

Upon investigation, the "Epic Status" values for the issues is as I'd expect; Done.

When I looked at the configuration for the Epic Status field, it appears that the configuration has been changed from the default set of To Do / In Progress / Done and now includes a number of other statuses.

I attempted to revert the change but the field is locked by the software. I'm curious to find out how I can revert it and also what caused the change - Changes to the field were not logged in the Audit Log so I'm not able to find out how this occurred. And even as a Site Admin, I am unable to edit the configuration.

We're on Jira Premium, and make use of Jira Product Discovery and Jira Plans

[MoroSystems Support]

[MoroSystems Support]

There is some bug in Atlassian community which restricts me from sending you this reply in text format, sorry for the inconvenience. :(

[Chris Martin]

THANKS a lot for the help! I was able to get the information I needed with your feedback. 

One of my big problems was that I don't have access to the database using mysqldeveloper, only PocketQuery. So it's a lot of trail/error and running select * statements to see what fields exist in what table. I've seen some JIRA documentation on the DB schema, but it seems to not include all tables. I'm going to install the trail version locally on my dev workstation. 

Thanks again @MoroSystems Support.. here's my final working query.

SELECT
 pra.roletypeparameter "Group",
 u.display_name "Name",
 pr.name "Project Role",
 p.pname "Project"
FROM
 projectroleactor pra
 LEFT OUTER JOIN projectrole pr ON pra.projectroleid = pr.id
 LEFT OUTER JOIN project p ON pra.pid = p.id
 LEFT OUTER JOIN cwd_user u ON u.user_name = pra.ROLETYPEPARAMETER
WHERE p.pname = 'my project name here'
ORDER BY p.pname;

[MoroSystems Support]

Thanks for sharing your query. I remember once trying to create an SQL query based solely on Jira DB documentation and well... never more. :) 

[Sven Schatter _Lively Apps_]

Hey CM,

great to see that your problem is solved. (You should probably accept MoroSystems answer to mark it as such)

Just letting you know that we have basically moved our support to our service desk for PocketQuery. So if you have any other problems, please don't hesitate to raise a ticket.

Thank you for using PocketQuery!

Best regards,
Sven (Scandio)