Supercharge Your Jira Workflow with Colored Label Manager!
- Sirine
- Atlassian
Tired of juggling messy labels and struggling to keep your Jira projects organized? With Colored Label Manager for Jira, you can take control like never before! 🎨✨
Our plugin doesn’t just color-code your labels—it supercharges them! Now, you can configure validator conditions and post functions directly with labels, turning them into powerful tools for automation, workflow control, and project management. Whether you’re enforcing rules, triggering actions, or streamlining processes, our plugin makes it easy and intuitive.
Introduction
👉 Here’s what you can do:
✅ Enforce rules effortlessly: Set up validator conditions to ensure labels are used correctly and consistently.
✅ Automate workflows: Use post functions to trigger actions automatically based on label changes.
✅ Simplify complexity: Manage multiple fields, colors, and configurations with admin-friendly controls.
✅ Boost productivity: Save time and reduce errors by automating repetitive tasks.
Ready to see how it works? Dive into our step-by-step guide below and discover how to configure validator conditions and post functions with labels using Colored Label Manager for Jira. Transform the way you work—one label at a time! 🚀
- 1 Introduction
- 1.1 Understanding Conditions in Jira Workflows
- 1.1.1 Use case
- 1.1.2 Integration Label in Workflow Condition
- 1.2 Workflow Configuration
- 1.2.1 Testing the Workflow
- 1.3 Understanding Validators in Jira Workflows
- 1.3.1 Use case
- 1.3.2 Integration Label in Workflow Condition
- 1.4 Workflow Configuration
- 1.4.1 Testing the Workflow
- 1.5 Understanding Post Functions in Jira Workflows
- 1.6 Use case
- 1.7 Workflow Configuration
- 1.7.1 Testing the workflow
- 1.1 Understanding Conditions in Jira Workflows
- 2 Conclusion
- 3 Need help?
Understanding Conditions in Jira Workflows
In Jira workflows, conditions are rules that determine whether a transition (e.g., moving an issue from one status to another) can be executed. They can be based on user roles, issue fields, or custom logic, ensuring only authorized users or valid actions are allowed .
Use case
We want that user to be able to transition the status of their ticket based on the "User Acceptance Testing" field.
If the User Acceptance Testing is set to Success, the user can only transition the ticket status from In Review to Done .
If the User Acceptance Testing is set to Fail, the user can only transition the ticket status from In Review to Code Review .
Integration Label in Workflow Condition
As a Jira Administrator you can Create a New Colored Label Field : “User Acceptance Testing “
-->Click on Add Colored Label Field, then set the name and description.As a Project Administrator you should add label items to your colored label field if it’s a restricted field see ( Restrict new label creation) .
Workflow Configuration
Add Condition: User Acceptance Testing = “ Success “ (Allow transition to Done)
Click on the Condition button.
Click Add Condition.
In our case we should check Value field then click Add :
In the field, select User Acceptance Testing, then choose the condition and value ("Success").
Click Add to apply the condition:
--> You should see something like this :
Add Condition : User Acceptance Testing = “ Fail “ (Allow transition to Code Review)
Click on Condition
Click Add condition :
--> You should see something like this :
In the field, select User Acceptance Testing, then choose the condition and value ("Fail") and Click Add to apply the condition
The condition already added , now we shouldclick on Publish draft :
You should see something like this :
Testing the Workflow
Create an issue
Make sure that you add the User Acceptance Testing field to the layout:
Go to Project Settings → Issues → Layouts.
Drag and drop the User Acceptance Testing field into the layout.
If the User Acceptance Testing field is empty, the user can only transition the issue to Reopened.
If User Acceptance Testing is set to Success, the issue can transition to Done.
If User Acceptance Testing is set to Fail, the issue can transition to Code Review .
Understanding Validators in Jira Workflows
In Jira, validators are rules that check whether certain criteria are met before allowing a transition (e.g., moving an issue from one status to another) to be executed. They ensure data integrity by validating fields, user inputs, or custom conditions, preventing invalid or incomplete transitions. For example, a validator can require that a "Due Date" is set before moving an issue to "Done."
Use case
In our case we will create a validator to prevent an issue from transitioning from Code Review to Deploy if the colored label field Server is empty .
Integration Label in Workflow Condition
Steps :
As a Jira administrator ; you should create a New Colored Label Field : “Servers”
-->Click on Add Colored Label Field, then set the name and description.As a Project Administrator , you sould add label items to your label field if it’s a restricted fieldRestrict new labels creation .
Workflow Configuration
Add Validator
Click on the Validators button.
Click Add Validator
In our case we will choose field required the click Add :
Add the field and a meesage then click Add
The validator already added, Click on Publish draft
--> You should see something like this :
Testing the Workflow
Create an issue on your project :
Once the Servers field is empty, the transition fails, and a pop-up message appears .
We add a value to the Servers field, then apply the transition, and it works
Understanding Post Functions in Jira Workflows
In Jira, post functions are actions that are automatically executed after a transition is completed in a workflow. They help automate processes and ensure consistency by performing tasks such as:
Updating issue fields (e.g., setting a resolution or priority).
Triggering notifications or emails.
Assigning issues to specific users or roles.
Adding comments or logging work.
Post functions are essential for streamlining workflows and reducing manual effort.
Use case
Whenever an issue is in the QA status and the User Acceptance Testing field is set to Fail, the field should be cleared when the issue transitions back to Code Review.
Integration Label in Workflow Post-Function
Steps :
Workflow Configuration
Add Post_Function
Click on Post_Functions
Click Add Post_Functions
In our case , we want to clear a field so we select “CLEAR FIELD VALUE “ then Click Add
Choose the field then click Add
The post_Function already added , then click on Publish Draft
--> You should see something like this :
Testing the workflow
"Create an issue, set User Acceptance Testing to 'Fail,' and set the status to QA.
Once we transition from QA to Code Review, the User Acceptance Testing field will be cleared
Conclusion
The Colored Label Manager plugin, combined with Jira's conditions, validators, and post functions, unlocks a new level of workflow efficiency and visual organization. By using conditions, you can control access to label-related transitions based on user roles or issue states. Validators ensure that only properly labeled issues move forward, maintaining data accuracy and consistency. Meanwhile, post functions automate actions like updating labels or notifying teams, saving time and reducing manual effort.
Together, these tools empower you to create structured, visually intuitive, and error-free workflows. Whether you're enforcing label restrictions, automating processes, or improving project clarity, the Colored Label Manager seamlessly integrates with Jira's workflow features to deliver a smoother, more productive project management experience.
Need help?
Please raise an issue in our Help Center in case of questions or to report a bug, we are here to support you.