Task color tag and text tags

With the premium account, you can add color tags and text tags to your project and recipe tasks. All tags are defined at the project task level and unique for that project. Tags are not automatically shared across projects.

How-To Video (4 minutes)

Color Tags (and Milestones)

Use cases: Use color tags to highlight tasks with visual cues, such as identifying which tasks are critical. For an Agile development sprint board, the colors could indicate bugs, rejected, features, etc.
Feature access: Project belonging to an organization.
User access: Any team member assigned to a task can select a task color, but cannot edit labels.
Tag label editing: Only a Project Admin or Workspace Admin.
Project uniqueness: When you edit a label, it only affects that project, so each project can have different labels.
Recipe access: You can set up recipe tasks with colors and color labels, which will carry over to your projects created from that recipe.

How to add a color tag to a task.

1. When you open your task, you will see a tag icon in the action button menu.
2. Click the tag icon to see the tags view. The default landing will be the COLOR TAG view as shown in the following screenshot.
3. Select a color tag. You can select up to three different colors.
4. Click update.
5. Task will now have a vertical color bar to the left of the task as a visual indicator.
   
   Special "Milestone" color tag. Although it's black and therefor not a color, we added it to this set of options since it fits well as an indicator item.
   See the help article on working with milestones.

As the Project Admin permission person, you will be able to change the color labels to anything label you like. For example, the following screenshot displays how we have labeled them for our Pie development Agile sprint project, which we happily use for building you this wonderful app. For example, we changed orange to "Bug" and red to "Critical Bug". Then we select this color for bug tickets in our sprint. For features, we don't use any color, but you could use a color for feature, but then all tasks on your sprint board would have some color (which is fine too).

Tips: A faster way to get to the color selection, is to hover over the task and click on the vertical bar to the left of the task. This will popup the same view. Notice our labels in the following image. We use purple to designate an import target for a story or bug task to get completed for this week's sprint. Sometimes a developer would have an idea for something not yet approved by the product manager, so we use green for that item. Blue is for "Rejected story or bug tickets during the QA board phase. The QA person will mark it blue, add comments, and drag the task back to Not Started for the developer to pick up again.

Text Tags

Use cases: Use text tags to provide keywords for future filtering, such labeling certain development team's set of requirements (stories) related to a certain features set (Epic).
Feature access: Project belonging to an organization.
User access: Any team member assigned to a task can add an existing tag to a task from a text tag dropdown list.
Tag label editing: Only a Project Admin or Workspace Admin.
Project uniqueness: When you create a text tag, it only affects that project, so each project can have different text tags.
Recipe access: You can set up recipe tasks with colors and color labels, which will carry over to your projects created from that recipe.

How to add a text tag to a task:

1. When you open your task, you will see a tag icon in the action button menu.
2. Click the tag icon to see the tags view. The default landing will be the COLOR TAG view.
3. Click TEXT TAG to the right of the color tag tab.
4. Click your mouse inside the "Create or select tags" field.
5. If there were previously created tags for this project, they would display in the dropdown for selection. A task owner (assignee) can select from the existing list.
6. As a Project Admin, you can start typing in the "Create or select tags" field to create a new tag label and hit enter to add.
7. Then click Update to update the task.
8. Note: You can add multiple tags to a task. You can remove them by clicking the "X" in the tab label.

The following screenshot shows how we added an epic tag for a new story ticket (new feature requirement) in our backlog slice of our Pie development Agile sprint project. We created a process box to contain all feature items related to reports. We then tagged then with this text tag. Then as things move through the sprints, I can easily filter the project to show only stories related to the set of report features (Reports Epic).