🚀 View and update weight

Problem

1. Several customers have vocalized the desire to add weight directly to an epic. This is useful when doing ROM (Rough Order of Magnitude) estimation before an epic is decomposed into smaller vertical slices and estimated by a development team.
2. As we move towards work items with Tasks as the first step, users will naturally want to be able to set a weight on a Task. Given that issues already have weight as a field, we need to consider how weight ought to behave within this new model.

Proposal

• A user can set a numeric weight on any work item into an Weight field.

In the example below, Tasks do not have a weight field. The same rollup calculations would be used if Tasks did not have a weight field.

UX

#362550[No_Rollup_-_Entered.png]

MVC 1 Acceptance Criteria

• A user can set an estimated weight on any work item.
• The weight must be a valid, positive, whole integer.
• Weight updates in real-time
• Snowplow event tracking
• Redis counter

Event tracking

Snowplow tracking label: item_weight

• name: users_updating_weight_estimate
• category: work_items
• redis_slot: users
• include in the following aggregation counters:
  • xmau_plan
  • xmau_project_management
  • xmau_product_planning
  • xmau_certify
  • users_work_items
  • new aggregate counter (name: replace with name of new aggregate counter here)
• documentation: Service Ping Implementation, Redis HLL Counters

Tier

• GitLab Premium as Weight is currently in this tier.

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.