Transition issues when assigned to a developer

Use case

When doing a lot of manual work, some steps can be forgotten from time to time, even if they are tightly related to each other, e.g. transitioning an issue to "In Development" when the assignee is changed to a user in the "Developers" project role. In this example we will configure a rule that will automatically transition those issues.

⚒️ Configuration

Field changed event

Create a new rule and name it appropriately.

Providing a description will help you to identify what the rule does but this step is optional.

Add a Trigger → Field changed event

Field

Choose Assignee

Changed to

Choose Any Value

No further configuration needed. The automation rule is triggered every time an issue is being transitioned.

User condition

Add Condition → User condition

User to evaluate

Choose User in field → Assignee

Check against

Choose User in Project role(s) → Developers

Transition issue action

Next to the User Condition click on Add → Action → Transition issue

Mode

Choose Transition to status → In Development

The target status has to be reachable from the current status, otherwise, the action will not be executed.

Run as

Choose User in field → Assignee

Enable the rule by clicking on the Enable button →

📹 Screencast

This is how the configuration above should look on your screen

📤 Import the example

Import the JSON file below to get started in no time.

JSON

After importing the JSON file, make sure to check the configuration of the rule. Non-existing configuration elements (issue types, fields, values etc.) will be highlighted.

JavaScript

{
    "name": "Transition issues when assigned to a developer",
    "description": "",
    "creator": "admin",
    "status": false,
    "triggerData": "",
    "triggerType": "FIELD_CHANGED_EVENT",
    "configuration": {
        "refs": [
            "issue",
            "system",
            "trigger.issue",
            "trigger.parent"
        ],
        "fieldId": "00003",
        "option": "any",
        "triggerType": ""
    },
    "children": [
        {
            "sequence": 0,
            "type": "USER_CONDITION",
            "ruleEntityType": "CONDITION",
            "configuration": {
                "refs": [
                    "issue",
                    "project",
                    "system",
                    "trigger",
                    "trigger.issue",
                    "trigger.parent"
                ],
                "userOption": "userInField",
                "userInField": "00003",
                "checkOption": "projectRole",
                "projectRole": [
                    "10001"
                ]
            },
            "children": [
                {
                    "sequence": 0,
                    "type": "TRANSITION_ISSUE",
                    "ruleEntityType": "ACTION",
                    "configuration": {
                        "refs": [
                            "issue",
                            "project",
                            "system",
                            "trigger",
                            "trigger.issue",
                            "trigger.parent"
                        ],
                        "option": "status",
                        "status": "10412",
                        "actingUser": "field_00020"
                    },
                    "children": null,
                    "hasChildren": false
                }
            ],
            "hasChildren": true
        }
    ],
    "hasChildren": true
}

📚 Related use cases

Title	Automated action	Label
Close tickets after version release	Transition issue action	STAFF PICK
Transition issues when assigned to a developer	Transition issue action
Transition affected issues when releasing a version (manually)	Transition issue action
Transition affected issues when releasing a version (automatically)	Transition issue action	STAFF PICK
Schedule the escalation of overdue issues	Transition Issue
Schedule issues for re-submission	Transition issue action
Resolve issues when all options of a checklist are checked	Transition issue action
Re-open issue when a new comment is added	Transition issue action
Keep the status of parents and sub-tasks in sync	Transition issue action	STAFF PICK
Close epic when stories are done	Transition issue action
Automatically close sub-tasks when parent is completed	Transition issue action	STAFF PICK
Close stories when epic is done	Transition issue action
Automatically close parent when all sub-tasks are done	Transition issue action	STAFF PICK