I'd like to propose a workflow that addresses some Jira hygiene topics:
- Link orphaned stories to epics, link orphaned epics to initiative (initiatives are in different projects than the epics). Check first if no such link
exists already. Not every epic links to an initiative but every story should be linked to an epic. If all choices of epics are less than 50% match,
suggest creating an epic.
- Activity summary - Every week I'd like to provide a summary for every epic and every initiative that I pick. This is done by looking at child-items
and seeing changes and comments from the past week, then creating a summary paragraph as a comment in the epic or initiative, respectively.
- Highlight tickets that are marked as "blocking" and are in my project
- Look for stale tickets in my project and closing them with a message saying "Due to lack of activity, this item has been closed. If you feel that it
should be addressed, please reopen it". Do this in bulk but cluster by ticket priority. The user will provide definitions of a "stale" ticket based on a
combination of priority and time-since-modified. Prompt the user to do so. Suggest defaults of 2 weeks.
- Highlight items that have not been triaged in over a week and suggest a triage outcome. This includes priority and moving the item into the backlog
(from "New"). this can be done by looking at similar items in the project
- Highlight tickets that are marked as "Blocking" where the blocked tickets are already closed. Suggest to close the ticket or break the link.
- Highlight tickets that are in progress but have no assignee.
- Highlight tickets with no "Activity type" value and suggest an activity type from the available values list for this field, based on semantic
analysis of the ticket that has no value assigned.
Feedback appreciated. I have a PR in my fork if anyone wants to take a gander: https://github.com/EliadCohen/ambient-code-workflows/tree/feature/jira_hygiene_workflows/workflows/jira-hygiene
I'd like to propose a workflow that addresses some Jira hygiene topics:
exists already. Not every epic links to an initiative but every story should be linked to an epic. If all choices of epics are less than 50% match,
suggest creating an epic.
and seeing changes and comments from the past week, then creating a summary paragraph as a comment in the epic or initiative, respectively.
should be addressed, please reopen it". Do this in bulk but cluster by ticket priority. The user will provide definitions of a "stale" ticket based on a
combination of priority and time-since-modified. Prompt the user to do so. Suggest defaults of 2 weeks.
(from "New"). this can be done by looking at similar items in the project
analysis of the ticket that has no value assigned.
Feedback appreciated. I have a PR in my fork if anyone wants to take a gander: https://github.com/EliadCohen/ambient-code-workflows/tree/feature/jira_hygiene_workflows/workflows/jira-hygiene