On this page

Use case

Often you do not only use Jira's basic set of features but extend your issues with custom fields like our calculated fields.

They work perfectly to aggregate data but once in a while you might want to do a reindex to get all up-to-date values from all issues.

In this use case we will perform an reindex on the current issue as soon as a custom field is updated.


 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 any custom field you want to listen to for changes

Changed to

Choose Any value

 Reindex issue action

Add Action → Reindex issue

No further configuration needed.


Screencast

This is how the configuration above should look on your screen

No screencast available at the moment


Import the example

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


JSON

{
    "name": "Reindex issue on custom field update",
    "description": "",
    "creator": "admin",
    "status": false,
    "triggerData": "",
    "triggerType": "FIELD_CHANGED_EVENT",
    "configuration": {
        "refs": [
            "issue",
            "system",
            "trigger.issue",
            "trigger.parent"
        ],
        "fieldId": "12202",
        "option": "any",
        "triggerType": ""
    },
    "children": [
        {
            "sequence": 0,
            "type": "REINDEX",
            "ruleEntityType": "ACTION",
            "configuration": {
                "refs": [
                    "issue",
                    "project",
                    "system",
                    "trigger",
                    "trigger.issue",
                    "trigger.parent"
                ]
            },
            "children": null,
            "hasChildren": false
        }
    ],
    "hasChildren": true
}



If you still have questions, feel free to refer to our support team.