Labels can be applied to issues, merge requests, and epics. Group labels are available for any project within the group.
Labels
-
Value (or impact) defines the extend to which Melusina or a certain area will benefit from the realization of the epic (3 high / 1 low)
-
Value (or impact) defines the extend to which Melusina or a certain area will benefit from the realization of the epic (3 high / 1 low)
-
Value (or impact) defines the extend to which Melusina or a certain area will benefit from the realization of the epic (3 high / 1 low)
-
the amount of work or conceptual challange of an epic (3 hight / 1 low).
-
the amount of work or conceptual challange of an epic (3 hight / 1 low).
-
the amount of work or conceptual challange of an epic (3 hight / 1 low).
-
The issue or epic is actionable but not yet included in an iteration. It is adequately scoped and sufficiently clear defined for an iteration and no dependency blocks it.
-
Summarize the result of the finished work in 1-3 sentences | Optionally, document new procedures or information in team docs | Write new insights or new work items, relevant for the parent epic, resulting from work on the issue as a comment to the parent epic | Re-consider the real weight of the issue after finishing
-
It is clear what work is necessary to realize the work item, how the final result and its components should look like (design in case of features) and if realization is realistically achieved in the turn of 1 iteration
-
Issues and work that appeared during iteration. If possible those issues should not be solved during iteration but only prepared and organized for future planing
Prioritized