Bulk edit the issue resolution

Use case

One major advantage of Jira is the creation and implementation of customized workflows. But as fast as new workflows are created, mistakes happen. A common misconfiguration is forgetting to set a resolution on the final workflow transition.

By default, in Jira you cannot bulk edit resolutions. With this rule you can!

Manual trigger

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 → Manual

No further configuration needed. The rule will only be executed if a user hits the Execute button .

JQL Selector

Add Selector → JQL Selector

JQL Query

Use the following Expression:

project = TIS and statusCategory = Done and resolution is empty
# Customize the JQL to your needs

Update field action

Next to the JQL Selector, click on Add → Action → Update field

Field

Choose Resolution

Update to

Choose Selected Value

Value

Choose one of the given resolutions (e.g. Done)

You can also use this rule to delete resolutions from issues that are obviously not done!

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.

{
    "name": "Bulk edit the issue resolution",
    "description": "",
    "creator": "admin",
    "status": false,
    "triggerData": "",
    "triggerType": "MANUAL",
    "configuration": {
        "refs": [
            "issue",
            "system",
            "trigger.issue",
            "trigger.parent"
        ],
        "actingUser": "field_00020",
        "triggerType": ""
    },
    "children": [
        {
            "sequence": 0,
            "type": "JQL_SELECTOR",
            "ruleEntityType": "SELECTOR",
            "configuration": {
                "refs": [
                    "system"
                ],
                "jql": "project = TIS and statusCategory = Done and resolution is empty",
                "jqlParsingMode": "jql",
                "actingUser": "field_00020"
            },
            "children": [
                {
                    "sequence": 0,
                    "type": "UPDATE_FIELD",
                    "ruleEntityType": "ACTION",
                    "configuration": {
                        "refs": [
                            "issue",
                            "issues",
                            "selector.issue",
                            "selector.parent",
                            "system"
                        ],
                        "fieldId": "00028",
                        "mode": "fix",
                        "value": "7",
                        "actingUser": "field_00020"
                    },
                    "children": null,
                    "hasChildren": false
                }
            ],
            "hasChildren": true
        }
    ],
    "hasChildren": true
}

Related use cases

Title	Automated action	Label
Inherit value from parent in Advanced Roadmaps hierarchy	Update field action
Copy excerpted value from new comments	Update field action
Bulk clear the issue resolution	Update field action	STAFF PICK
Add components of the epic to the current issue	Update field action
Sum up value in parent issue on field change in sub-tasks	Update field action
Delete the attachments of an issue 30 days after closing it	Update field action
Update assignee and reporter to facilitate user deletion	Add comment action Assign issue action Update field action	STAFF PICK
Bulk edit the issue resolution	Update field action	STAFF PICK
Keep the priority of parents and sub-tasks in sync	Update field action