Improve automation in Issue Boards
Actionable Insights
Actionable insights always have a follow-up action that needs to take place as a result of the research observation or data, and a clear recommendation or action associated with it. An actionable insight both defines the insight and clearly calls out the next step. These insights are tracked over time.
Link
-
Provide the link to the Dovetail actionable insight you created earlier (this should contain all the essential details) -
If applicable, link this actionable insight issue back to the original Research Issue in the GitLab UX Research project
Assign
-
Assign this issue to the appropriate Product Manager, Product Designer, or UX Researcher
Description
-
Provide some brief details on the actionable insight and the action to take
PLEASE COMPLETE THE BELOW | |
---|---|
Dovetail link: | https://dovetailapp.com/projects/61a6277b-7f54-45bc-907b-a8b1ec2be4eb/insights/present/b111127e-2708-4684-ac63-d55fee45172c |
Details: | Users want to see more automation in Issue Boards to reduce the burden of manually managing Issue metadata (e.g. labels, assignees, time issues spend on the board, etc). They would like the ability to set up rules that are based on workflow. |
Action to take: | Build automation into Issue Boards. Related issues: #214402, #17334, #2059 |
Additional Context
- "If an issue is labeled 'x' and then labeled 'y' do 'z'." You can take a look at Azure DevOps to see a great setup. Some examples from our workflow: - If an issue's label changes from 'c::READY TO BEGIN' to 'c::IN PROGRESS', assign the current user - Prevent an issue from moving from 'c::IN PROGRESS' to 'c::READY FOR CODE REVIEW' if the issue still has incomplete tasks"
- Aging: The Issue Board could start changing color based on amount of time issues have spent on the board. This would help them quickly look at the board and see the status of the items. Azure DevOps as an example of aging.
~"Actionable Insight"
Edited by Katherine Okpara