The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

To hide Closed Epics from backlog view, they should not be linked to `Won't Do` stories. Why?

Brice Laurencin
January 2, 2024

Following this announcement, I tried to understand why some of the epics would still be listed on the backlog view.

It appears that if a `Done` epic contains only `Realeased` (a.k.a. `Done`) stories, it does not show in the epic panel of the backlog view.

If the epic contains a single `Won't Do` story (another `Done` state in our configuration), the epic is shown in the epics panel of the backlog view.

Why is that? did we miss something in our setup?

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Marc -Devoteam-
Community Champion
January 2, 2024

Hi @Brice Laurencin 

Welcome to the community.

It could be that it's because of the following reason stated in the announcement.

"If you have epics whose Epic status is marked as Done but the epic’s Issue status category is not Done, these epics will re-appear on your backlog epic panel."

Is the Epic containing in 'Won't Do' story in the issue state 'Done"?

Brice Laurencin
January 2, 2024

Yes, everything is `Done`.

When I remove the `Won't do`'s from the epic, it instantly disappears from the panel.

Marc -Devoteam-
Community Champion
January 2, 2024

Hi @Brice Laurencin 

As you mention Won't Do is also a Done status category, this should work the same as done.

I tried it with issue type with different workflows and different Done statuses in the workflow of the issue type and it all worked as expected.

So i places all epic child issues to a done state and then set the epic to done and the epic is then gone from the backlog.

Might it be an automation on your project, as it is strange that this only happens when all issues are set to Done and not another Done state.

Add also seems to happen directly when you set the epic child's to done and you don't have to action on the Epic.

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events