Edit-tag
Jump to navigation
Jump to search
A Tag is an informative label attached to tasks. Tags have no effect on planning or execution.
Contents
Creating a tag
- Open Author → Tags.
- Click the create button above the list.
- Enter the name and description, then click Save.
Fields
| Field | Notes |
|---|---|
| ID | Assigned automatically; read-only. |
| Name | Mandatory and unique. Maximum 100 characters; letters, digits, space and _, -, /.
|
| Enabled | Whether the tag is available for assignment. |
| Description | Free text. |
Assigning tags
Tags are not assigned here. A tag is attached to a task in the task editor, from the Add tag... box in the Tags section; assigned tags appear as chips with a remove button. See edit-task.
Assignment takes effect immediately — it is not part of the task's Save action.
A task may carry any number of tags.
What tags are for
The usual scheme is to tag tasks by the consumer of their data, so a shared task carries every tag that applies:
ETL_CUSTOMER— tagged Sales and AccountingETL_ORDER— tagged SalesETL_PROFITLOSS— tagged Accounting
Tags are then used to filter the Monitor console down to the tasks feeding one consumer, and to aggregate processing statistics.
Practical notes
- Decide on a scheme before creating tags. Tags are cheap to add and awkward to rationalise later, and a set that mixes several schemes — some by department, some by technology, some by ticket — stops being useful for filtering.
- Use a Group, not a tag, to affect execution. Tags create no dependencies, influence no priority and are not considered by any limit.
- Disabling a tag keeps existing history intact while taking it out of use.