Jira Automation: Difference between revisions
imported>Unknown user No edit summary |
No edit summary |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Jira automation is a feature that allows users to automate repetitive tasks and processes within Jira. It helps streamline workflows, reduce manual effort, and ensure consistency in task management. Automation rules can be set up to trigger actions based on specific events, conditions, or schedules. | |||
<span id="key-components-of-jira-automation"></span> | |||
=== Key Components of Jira Automation: === | |||
# '''Triggers''': Events that start the automation rule (e.g., issue created, issue transitioned). | |||
# '''Conditions''': Criteria that must be met for the rule to execute (e.g., issue type is a bug). | |||
# '''Actions''': The tasks that are performed when the rule is triggered and conditions are met (e.g., send an email, update an issue field). | |||
<span id="how-to-configure-jira-automation"></span> | |||
=== How to Configure Jira Automation: === | |||
# '''Access Automation''': | |||
#* Navigate to your Jira project. | |||
#* Click on "Project settings" in the sidebar. | |||
#* Select "Automation" from the settings menu. | |||
# '''Create a New Rule''': | |||
#* Click on the "Create rule" button. | |||
#* Choose a trigger from the list (e.g., "Issue created"). | |||
# '''Add Conditions (Optional)''': | |||
#* After selecting a trigger, you can add conditions to refine when the rule should run. | |||
#* Click on "New condition" and select the type of condition you want to apply. | |||
# '''Define Actions''': | |||
#* Click on "New action" to specify what should happen when the rule is triggered and conditions are met. | |||
#* Choose the action type (e.g., "Edit issue", "Send email"). | |||
# '''Test the Rule''': | |||
#* Before activating the rule, you can test it to ensure it works as expected. | |||
#* Use the "Audit log" to review the results of the test. | |||
# '''Save and Enable the Rule''': | |||
#* Once you are satisfied with the configuration, save the rule. | |||
#* Make sure to enable it so that it starts running. | |||
# '''Monitor and Adjust''': | |||
#* Regularly check the audit log to monitor the rule's performance. | |||
#* Adjust the rule as necessary based on feedback and changing requirements. | |||
By using Jira automation, teams can enhance their productivity and focus on more strategic tasks rather than getting bogged down by repetitive manual processes. | |||
<span id="example"></span> | |||
=== Example === | |||
A common automation / rule is adding a label to an issue when it is transitioned from QA to in progress. | |||
* '''Trigger:''' Work item transitioned | |||
* '''From''' QA '''to''' In progress | |||
* '''Then''' Edit work item field (label) | |||
** select '''label''' | |||
** on the three dots next to dropdown, select ADDREMOVE | |||
** type “no_qa” (labels can’t have spaces) | |||
That’s it. | |||
You can create another rule for removing the tag when issue transitions from QA to Ready to deploy. | |||
'''IMPORTANT:''' current issue tags are not dynamically updated in the boards when drag and dropped. Page needs to be refreshed. | |||
[[Category:Jira management]] | |||
Latest revision as of 12:10, 22 October 2025
Jira automation is a feature that allows users to automate repetitive tasks and processes within Jira. It helps streamline workflows, reduce manual effort, and ensure consistency in task management. Automation rules can be set up to trigger actions based on specific events, conditions, or schedules.
Key Components of Jira Automation:
- Triggers: Events that start the automation rule (e.g., issue created, issue transitioned).
- Conditions: Criteria that must be met for the rule to execute (e.g., issue type is a bug).
- Actions: The tasks that are performed when the rule is triggered and conditions are met (e.g., send an email, update an issue field).
How to Configure Jira Automation:
- Access Automation:
- Navigate to your Jira project.
- Click on "Project settings" in the sidebar.
- Select "Automation" from the settings menu.
- Create a New Rule:
- Click on the "Create rule" button.
- Choose a trigger from the list (e.g., "Issue created").
- Add Conditions (Optional):
- After selecting a trigger, you can add conditions to refine when the rule should run.
- Click on "New condition" and select the type of condition you want to apply.
- Define Actions:
- Click on "New action" to specify what should happen when the rule is triggered and conditions are met.
- Choose the action type (e.g., "Edit issue", "Send email").
- Test the Rule:
- Before activating the rule, you can test it to ensure it works as expected.
- Use the "Audit log" to review the results of the test.
- Save and Enable the Rule:
- Once you are satisfied with the configuration, save the rule.
- Make sure to enable it so that it starts running.
- Monitor and Adjust:
- Regularly check the audit log to monitor the rule's performance.
- Adjust the rule as necessary based on feedback and changing requirements.
By using Jira automation, teams can enhance their productivity and focus on more strategic tasks rather than getting bogged down by repetitive manual processes.
Example
A common automation / rule is adding a label to an issue when it is transitioned from QA to in progress.
- Trigger: Work item transitioned
- From QA to In progress
- Then Edit work item field (label)
- select label
- on the three dots next to dropdown, select ADDREMOVE
- type “no_qa” (labels can’t have spaces)
That’s it.
You can create another rule for removing the tag when issue transitions from QA to Ready to deploy.
IMPORTANT: current issue tags are not dynamically updated in the boards when drag and dropped. Page needs to be refreshed.