Save/Update Rules Permission Check

Save/Update Rules Permission Check

When creating or updating an automation rule in the Sprint Scheduler app, the user must have the required Jira permissions on all projects associated with the selected board.

If the required permissions are missing, the app will display an error message and the rule cannot be saved or updated.


Required Permission

The user must have the following Jira permission:

  • Manage Sprints

This permission is required for every project included in the board.


Why This Happens

A Jira board can reference issues from multiple projects.

For example:

  • Project A

  • Project B

  • Project C

Even if the user has Manage Sprints permission on:

  • Project A ✅

  • Project B ✅

But does not have permission on:

  • Project C ❌

The Sprint Scheduler app will still block the save/update operation and display an error.

The permission check applies to all projects referenced by the board.


Troubleshooting Steps

1. Identify All Projects Used by the Board

  1. Open the Jira board

  2. Go to:

    • Board Settings

  3. Review the board filter/query to identify all projects included in the board

Example:

project in (PROJA, PROJB, PROJC)

In this example, the user needs the required permission on:

  • PROJA

  • PROJB

  • PROJC


2. Verify “Manage Sprints” Permission

For each project referenced by the board:

  1. Go to:

    • Project Settings → Permissions

  2. Locate:

    • Manage Sprints

  3. Verify that the affected user (or their group/role) has this permission


Important Note

Having permission on only some of the projects is not sufficient.

If even one project associated with the board is missing the Manage Sprints permission, the Sprint Scheduler app will continue to show an error during:

  • Rule creation

  • Rule save

  • Rule update


Recommended Fix

Ensure that the affected user has:

  • Manage Sprints permission

  • On every project referenced by the board filter

After updating permissions:

  1. Refresh the Sprint Scheduler app

  2. Try saving or updating the automation rule again