---
title: "9. Best Practices"
canonical: "https://support.covectors.io/space/CTFJ/1581514753/9.%20Best%20Practices"
format: markdown
---
Maximize the value of **JCT **by following these simple best practices.

##  Labels & Groups

- **Plan your labels:** Use clear, distinct names; avoid duplicates. Example for group names: *Delivery Workflow*, *Customer Requests*, *Internal Decisions*.
- **Create meaningful groups **by following the creation** **workflow: **Create group → Add labels → Assign to projects**.
- **Use colors:** Helps scan long comment threads easily.
- **Retro-compatibility:** Old labels appear under *Ungrouped*; move them to new groups for better organization

## Label Roles & Permissions

- **Separate responsibilities:** Prevent uncontrolled label creation.
- **Review roles periodically** to maintain consistency.

**Who defines roles? :** Instance Admins, Organization Admins, and Jira Admins can decide who has access to manage label roles and permissions.

**Who manages labels:** Users granted access to manage labels, roles, and permissions can then decide who can:

- Create, edit, delete, and archive labels
- Manage label groups (and assign to projects)
- Use labels on comments within their assigned project


## Adding & Updating Labels

- **Assign multiple labels to a comment **when relevant.
- **Archive, don’t delete, if **you’re unsure — as it preserves data.


- keep label names short & clear
- Periodically review zombie/ unused labels
- structure labels around workflows, not emotion  
(e.g., “Need Backend Support” is better than “Why is this broken”)

## Maintenance

- Review groups and labels regularly to keep your labels relevant
- Archive unused labels; move/rename thoughtfully