Auto‑Assign Jira Issues on Custom Field Change

Goal

When a specific custom field is edited, you want Jira Cloud to automatically assign the issue to a predetermined user. This guide shows how to create a project‑level automation rule that does exactly that, checks that it worked, and tells you how to stop it if it behaves unexpectedly.

Prerequisites

• Jira Cloud instance 2026.3 or newer.
• Project administrator or higher permission to edit automation rules.
• Target user (e.g., jane.doe) must have the Edit Issues permission in the project.
• Custom field already created (e.g., Project Lead of type "User Picker").

Step‑by‑Step Procedure

1. Navigate to Automation

   Project Settings → Automation

   Alternatively, for a global rule, go to System → Automation. This example uses a project rule.

2. Create a New Rule

   Click "Create rule" → Name it "Assign to Project Lead on Field Change"

3. Add Trigger: Field Value Changed

   Select "Field value changed" → Pick the custom field (e.g., Project Lead) → Click "Save"

   This trigger fires whenever the field’s value changes.

4. Add Condition: Assignee is not Target User

   Add "If" → "Assignee" → "is not" → Enter target username (e.g., jane.doe)

   Prevents the rule from re‑running when the assignment action itself changes the monitored field, avoiding infinite loops.

5. Add Action: Assign Issue

   Add "Assign issue" → Choose user "jane.doe" → Click "Save"

6. Enable the Rule

   Toggle the rule to "Enabled" → Confirm the confirmation dialog

7. Save the Rule

   Click "Publish" to activate the rule

Expected Outcome

After the rule is enabled, any change to the Project Lead field on an issue in the project should trigger Jira to assign that issue to jane.doe. The assignment change is logged in the issue’s activity stream and in the Automation audit log.

Verification

1. Create a Test Issue

   Project → Create → Fill required fields → Leave "Project Lead" empty → Click "Create"

2. Change the Monitored Field

   Edit the issue → Set "Project Lead" to any value (e.g., "Team A") → Save

3. Check Assignment

   Issue view → Look at the Assignee field; it should now show "Jane Doe"

4. Inspect Audit Log

   Automation → View audit log → Find the rule execution → Confirm status "Success" and assignee change

Common Pitfalls & Mitigations

• Infinite Loops: If the custom field is a user picker and you assign the issue to that same user, the rule might fire again. The condition added in step 4 stops this by checking the current assignee.
• Permission Errors: The rule fails silently if the target user lacks Edit Issues permission. Verify permissions before enabling.
• Quota Exhaustion: Automation rules consume execution quota. If the rule triggers on very frequent field changes, monitor the System → Automation quota dashboard.
• Global vs Project Scope: A global rule would apply to all projects. Keep the rule scoped to the specific project to avoid unintended assignments.

Rollback & Recovery

If the rule misbehaves, you can:

• Pause the Rule: In the rule list, click the three‑dot menu → Pause. The rule stays in the system but stops executing.
• Delete the Rule: If you no longer need it, choose Delete from the same menu.
• Review Audit Log: The audit entries show why a rule failed (e.g., permission denied). Use this information to adjust permissions or the rule logic.

Conclusion

By following this guide, you can reliably automate issue assignment based on a custom field change in Jira Cloud. The rule is lightweight, easy to audit, and reversible, ensuring minimal disruption when the business logic changes.