This page documents different automation rules you can configure in Jira.

Add field values

Apply a QA label

When an issue is created WHERE the issue type = spike THEN input the “QA” label into the “Labels” field

  • Variation: When the issue is transitioned OR the sprint value is set WHERE assignee = {QA Team Member} THEN input the “QA” label into the “Labels” field

Apply a Team value

When the assignee changes WHERE JQL matches the following query created >= startOfYear() and type in standardIssueTypes() and assignee in (62104a4ef97d18007175cb68...) AND "Team[Team]" = EMPTY and project NOT IN ("Sample Scrum Project") THEN Advanced edit the issue:

{
"fields": {
"team": "0632fde3-f54b-4bfe-9e44-e2580deec56a"
}
}

Leave a comment

Comment on a newly created incident

When an issue is created WHERE issue type = incident THEN add a comment to the issue:

Incident reminders:
- Incident process documentation: LINK
- Incident issue type template: LINK
- The incident issue type is similar to a spike and assigned to the incident manager. Create linked tasks, bugs, or spikes to represent the actual work.
- The incident manager is the PO for the affected product.
- Sev 1 & Sev 2 should be added to the current sprint since they are very urgent.
- Create a linked postmortem document.
- Notify relevant team members in the #relevant-slack channel
- Add labels when relevant.
- Good luck!

Transition an issue

A blocked child issue transitions the parent to blocked

When an issue is transition to “Blocked” WHERE issue type = Task FOR linked issues = “blocks” WHERE issue type = Story THEN transition (parent) issue to status = “Blocked”