Why do Archived Issues still show up in Epics under 'Issues in Epic'?

[Dakota Bramblette]

We recently switched over from Delete to Archive (disabled Delete but enabled Archive in its place) and we noticed an odd incident when looking at Epics. 

If you archive an issue, it is removed from the index, queries, etc. However, if you are on the Epic View screen, under the tab 'Issues in Epic' archived issues are present and do not give any indication it was archived and considered irrelevant. 

Has anyone else seen this? I don't believe they should show up there or at the very least be grayed out if the idea is to give users the option to restore from this section.

[Raleigh]

Just came across this today. Was hoping archiving Canceled stories in the Epic would clear them out to declutter the Epic. Looks like the only option is to remove them from the Epic but label them in some way to see that they were in the Epic. Means more labels and remembering, but that may be it.

[Lawrence C_ Loteria]

I also just encountered this. Hope there's already asolution or an answer at least. 

[Shweta Singh]

No support on this so far?

[Jamie]

Just noticed this with a recent shift into "archiving" rather than deleting issues.

I can't believe this is something that Atlassian describes as "working as intended". 

I have provided the following feedback to Atlassian, I do hope they either listen (or have this on their radar already)

......

You have missed some key changes to how archived issues are handled.
For example, an archived issue should be removed from child issues. The epic should be ignoring it but it is not. You still have it appearing in the Child issues list like it is still relevant, and also still utilising it as part of the progress logic for an epic when it should not.

For example, I had 4 child issues in an Epic. 2 of which have been "archived", 1 is in progress and the other is still in To-Do. Yet your progress logic states 3 of 4 issues "To-Do". Wrong. It should state 1 of 2 issues To-Do, ignoring the archived issues. These archived issues should not even be in the list.

If the issue is archived, it should effectively be a soft delete, like it had been deleted but you can still directly access it to restore it and its data to the instance.

[Jamie Rogers]

I queried this with Atlassian Support and they advised this is 'working as intended' however there is a feature request on their backlog to better improve visibility of archived issues on Epics.

JRASERVER-71119