Add ability to edit health status in Issue sidebar

Problem to solve

As a User of Epics and Issues,

I need to be able to understand the current health status of work I am following,

So I can respond to delays, problems, and reassign the proper resources.

Review gitlab-com/Product#593 (closed) for internal use case and context.

Intended users

  • Parker (Product Manager)
  • Delaney (Development Team Lead)

Solution

⭐ A. Future scope, complete MVC
  • User can add or remove "Health status" from the sidebar, within a dropdown.
  • Once applied, the Health status appears a badge that is consistent with the badges in the epic tree.
  • For MVC, the badge doesn't navigate the user anywhere (eventually it may go to a filtered list of issues).
  • On hover, the badge triggers a tooltip that explain what the health status means, ie "This attention is on track. On track issues -insert description of on track here-."
⭐ :B. MVC
  • User can add or remove "Health status" from the sidebar, within a dropdown.
  • Once applied, the Health status appears as text within the dropdown.
  • For MVC, the badge doesn't navigate the user anywhere (eventually it may go to a filtered list of issues).
  • On hover, the badge triggers a tooltip that explain what the health status means.
  • On hover, the badge triggers a tooltip that explain what the health status means, ie "This attention is on track. On track issues -insert description of on track here-."
⭐ :C. First iteration toward MVC
  • User can add "Health status" from the sidebar, within a dropdown.
  • User can remove Health status from the sidebar via the -remove status pattern next to the dropdown input.
  • Once applied, the Health status appears as text within the dropdown.
  • For MVC, the badge doesn't navigate the user anywhere (eventually it may go to a filtered list of issues).

Further details

Health Status = Traditionally represented in other tools in the market as Green/Yellow/Red

Screen_Shot_2019-12-11_at_2.39.43_PM

Risk Management Plugin for JIRA

Necessary Usage Data

To track adoption and success we need to be able to view the # of issues with a health status in a Periscope view. Moved this to a followup issue

Future Iteration Considerations

Risk Status Automation

  • We should investigate any opportunity to enable automated risk statuses leveraging data in GitLab like assigned milestone dates, weight completed, time tracking, etc
  • Possibly provide the ability to set custom rules for automating transitions into each risk stage

High Level Risk Reporting

  • We should investigate the best way to surface/report risk at a Project and Group level, aggregating risk status from multiple epics and presenting it in a single view.

Questions asked during Problem Validation:

  • How are users currently tracking Health Status of work?
    • Via comments or updates to description
  • What are the pros/cons of those approaches^?
    • Major cons are the inability to quantify health up a chain of hierarchy or view it anywhere else in the tool
  • How do users expect to view and analyze Health Status over many issues and epics?
    • General consensus is at the Epic Level they'd like to see an aggregate health metric and see each issue's health displayed within the Epic Tree view
Edited Mar 30, 2020 by Alexis Ginsberg
Assignee Loading
Time tracking Loading