When you clone a Resolved ticket, Atlassian naturally resets the workflow status to Open. The same should happen with the Epic Status field. Users get bit by this when their Epics don't appear on their agile boards or in the Epic Link dropdown field because Jira considers these Epics Resolved.
In addition, any scripts you run against the Epic will throw an error against a Resolved Epic unless you capture and code for Resolved Epics.
A new Bug ticket has been generated for Atlassian to fix this issue. An Original Bug ticket was submitted 4 years ago. With no work done against the original ticket, Atlassian downgraded the ticket to a "Suggestion".
Please help get this issue resolved by voting for
Yes, and...If this suggestion gets implemented a work-around would be to reset the epic status using an automation rule when an epic is created. I wonder which of these items will be implemented first: the defect or the suggestion. :^)
Hello Community! My name is Brittany Joiner and I am a Trello enthusiast and Atlassian Community Leader. In this video, I'll share my favorite Trello templates. Templates mentioned in ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events