Currently, when we are done with an Epic issue, we want to mark both the Issue itself and the instance in our backlog as "Done". I'm in charge of automating this, where marking the Issue page as "Done" automatically removes it from the backlog.
We have a few scripts, in Python, running off webhooks on another server. I was planning on setting up another webhook in the Epic's workflow transitions, but after looking around in the Jira-Python API documentation, I couldn't find anything that could manipulate the backlog. Is there another way to automate this process?
The Issue Workflow likely has a "Closed" status, something like that. Marking a Epic as "Done" on the backlog is done by setting the field Epic Status to "Done".
You just need to make sure that you update the Epic Status customfield to DONE when moving to CLOSED and that you move it back to TO DO when you reopen the ticket.
This does leave a hole though. It's possible to open and close the epic status field with the workflow, but if someone marks and epic as Done via the board, the issue status won't update automatically.
You could add a listen to handle this case.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs