Cloning an Epic should reset the Epic Status field

[Jeanne Howe]

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
https://jira.atlassian.com/browse/JSWCLOUD-21102

Thank you

[Alexander Bondarev]

Hi, @Jeanne Howe !

Voted ✅

[Bill Sheboy]

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.  :^)

https://codebarrel.atlassian.net/browse/AUT-1959

Best regards,

Bill