Work Item Quick Action: Blocks and Blocked_by

Release Notes

The new quick actions for work items /blocks and /blocked_by enables you to create bidirectional blocking relationships between work items for improved dependency mapping and progress tracking.

Summary

To maintain consistency across our platform, we are introducing two new quick actions for work items: /blocks and /blocked_by. These actions will create bidirectional blocking relationships between work items, allowing for clearer dependency mapping. Similar to other quick actions we've implemented, these will also accept one or multiple work item iids, references, or URLs as parameters.

Current Behavior

Blocked_by	Blocks

Acceptance Criteria:

1. The /blocks quick action allows users to indicate that the current work item blocks another work item. Users can enter /blocks followed by one or multiple work item iids, references, or a URL in the comment box or the description.
2. The /blocked_by quick action allows users to indicate that the current work item is blocked by another work item. Users can enter /blocked_by followed by one or multiple work item iids, references, or a URL in the comment box or the description.
3. Upon execution, the system should validate the existence and accessibility of the target work items. If any issues arise, such as non-existence or permission constraints, a clear error message should be displayed.
4. Implementing these quick actions should follow the existing permissions and visibility settings for the work items involved.