Bug report: Epic Filter in Backlog broken after Project Key change

Bryan_8hl9wd

Steps to recreate:

1. click backlog in SCRUM project
2. Click "show epic panel" in Epic dropdown in Backlog view. Epics should populate
3. in Project Settings change project key to something new and delete old project key
4. Refresh backlog view and try to see epic panel again, epics will not populate
5. Try to add a new epic in the epic panel and see that the new one won't populate
6. Change the project key back to the old key and delete old project keys
7. Go back to backlog and refresh, notice that epics populate now

I'm guessing the epic filter in the backlog view is only set on creation of the project but not updated when project key changes.  

Please fix

Trudy P Claspill

Hello @Bryan 

Welcome to the Atlassian community.

Working with a Scrum board that uses a filter for a Company Managed Software project the filter looks like this:

project=ASP order by Rank ASC

If I change the project key and delete the old key then I have the same experience as you; the issues are listed in the backlog but the Epics panel is empty.

When I look at the Board Configuration the filter still shows project=ASP. However if I open that filter for editing it says the filter is invalid because the project key ASP doesn't exist.

If I update the filter to use the new project key, then the Epics panel in the Scrum board works again.

I didn't find anything in the Atlassian public backlog specifically about the breaking of the Epics panel. I did find these two issues related to the impact of deleting old project keys:

https://jira.atlassian.com/browse/JRACLOUD-84861

https://jira.atlassian.com/browse/JRACLOUD-85644

Documentation about changing project keys warns that it can impact filters but there is nothing specific about breaking the Epics panel while the issue list still works.

I have opened a support case with Atlassian to find out if there is already a bug or change request or documentation about this, and to get such created if not.