Hi,
We deployed a release and I wanted to close Epics associated with that release. I went into Epic panel and selected "Mark as Done". I go back to the backlog after all the clean up and see that all previously closed user stories associated with those closed Epics are now in the backlog. Using JIRA cloud.
Is this a bug, or how can we fix this?
Hello @Eleanor Tsang
I tried your scenario in my instance and i have the same result, so i think that is how is work.
The issue diplayed in the board come from a filter. That being said, "Mark as done" option change the epic status and not the issue status.
You'll need to write a query that will find stories link to an epic that have an epic status = Done.
But to write this query you will need an addon like scriptrunner
Hope this helps.
Thanks, @Mohamed Benziane .
From a product standpoint, why would this be working as expected and not a bug? Closed user stories and closed Epics should be closed and not pulled back into the backlog.
Also, wondering if this is happening to anyone else or if it's our board configuration as I'm trying to search similar issues in Community and not seeing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Actually, never mind. It was another configuration of the board that impacted user stories appearing in backlog.
Closing issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dear @Eleanor Tsang - the closed stories appeared in my backlog starting from last sprint. What was the configuration change you made and how it's get fixed? Please suggest.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.