Enhance Blocked Status Visualization for Improved Workflow Efficiency

Summary

Currently when a work item (issue, epic, task, objective, key result) is marked as blocked by another work item, the visualizations throughout GitLab Plan features accurately reflect the blocked status. However, once the blocking work has completed, we do not automatically update the blocked status, leaving users with potentially outdated and confusing information.

To address this, we should dynamically indicate when an item is no longer blocked. By automating the update of blocked statuses, users will experience improved visibility into the progress of their workstreams. This feature not only enhances the accuracy of project tracking but also enables teams to respond swiftly to changes in their workflow, ultimately boosting overall efficiency. Users can rely on up-to-date information to make informed decisions and prioritize tasks effectively.

Common User Stories

  1. As a Product Manager at GitLab, I want to effortlessly track the progress of workstreams, so I can manage product timelines effectively and foster a more streamlined product development process.
  2. As an engineering manager, I want to quickly identify when a workstream is no longer blocked, so I can efficiently allocate resources and plan the team's next steps.
  3. As a developer, I want my task board to accurately reflect the status of my work, so I can prioritize and focus on unblocked tasks.
  4. As an engineering manager, I want visualizations that dynamically update, ensuring that the team is always aware of changes in the project status, promoting collaboration and timely communication.

from GitLab team member

I wanted to provide some feedback on an experience that as an end user of Plan is confusing. Note I tried searching devops:Plan issues but wasn’t able to find a related issue but could’ve missed it. We utilize the “Block by” function to understand the order of our work which is great. However, when the blocking issue is closed i.e. no longer blocks the subsequent issue it remains in the issue as “is blocked by” and lists a closed issue. This leaves us with two options ignore the “is blocked by” section which isn’t ideal or deleting the original block but then we loose the linkage of our work. It could be nice to have it broken down by “currently blocked by” and “Previously blocked by” sections so it’s clear how the work has progressed.

example issue

Screenshot_2023-10-30_at_1_24_54_p_m_

Related

Edited by Amanda Rueda