Content
View differences
Updated by Rosanna Sibora 3 days ago
* ~~Work package categories are renamed to "labels"~~
* WL: OpenProject's **Categories** are more similar to Jira's **Components** and not the right fit for Jira labels.
* They are scoped to the project.
* The can have a default assignee, similar to Jira's **Components**.
* Labels can be added to work packages by any project user with wp edit rights
* There is a new field active per default in any wp type called "Labels"
* While typing in, a user gets a list of label suggestions based on the labels available within the project.
* A user should be able also to add fully new labels. While adding a fully new label we should visually indicate that this is a new label which will be added to the project.
* Permissions
* View labels: view work packages
* Add/remove labels (within the work package): Edit work packages
* Delete labels (from project): project admin
* Work packages can be filtered, sorted and grouped by labels.
* Labels are shown in the work package list.
* Users can filter for labels within backlog and sprints view.
* Project admin can view and manage in the project settings labels available in a project
* for each label there is a link to the wp table showing all wp associated with this label
* project admins can decide to delete a certain label. When deleted by an admin the label will be removed from all wp.
* project admins can edit a label (e.g. when a typo was done)
* in case the correctly written labels already exists, we should merge the corrected and the originally correct one into one label (a warning / explanation should be shown to the user). The typo use case is a very common one.
* project admins can archive a label: a label will not be shown in autocomplete anymore. Will be still however visible within the wp already associated with this label.
* WL: OpenProject's **Categories** are more similar to Jira's **Components** and not the right fit for Jira labels.
* They are scoped to the project.
* The can have a default assignee, similar to Jira's **Components**.
* Labels can be added to work packages by any project user with wp edit rights
* There is a new field active per default in any wp type called "Labels"
* While typing in, a user gets a list of label suggestions based on the labels available within the project.
* A user should be able also to add fully new labels. While adding a fully new label we should visually indicate that this is a new label which will be added to the project.
* Permissions
* View labels: view work packages
* Add/remove labels (within the work package): Edit work packages
* Delete labels (from project): project admin
* Work packages can be filtered, sorted and grouped by labels.
* Labels are shown in the work package list.
* Users can filter for labels within backlog and sprints view.
* Project admin can view and manage in the project settings labels available in a project
* for each label there is a link to the wp table showing all wp associated with this label
* project admins can decide to delete a certain label. When deleted by an admin the label will be removed from all wp.
* project admins can edit a label (e.g. when a typo was done)
* in case the correctly written labels already exists, we should merge the corrected and the originally correct one into one label (a warning / explanation should be shown to the user). The typo use case is a very common one.
* project admins can archive a label: a label will not be shown in autocomplete anymore. Will be still however visible within the wp already associated with this label.