Two-project sync - permissions setup

Who reads and writes

Sync runs call Jira as the app, not as a user. Only comments and attachments can be written under another identity, and you choose it per sync:

Identity When it is used
App Every read and every issue create, edit and transition. Also comments with Author = app (the default) and attachments with Upload as = app
Original author Comments with Author = original and attachments with Upload as = original (the attachment default) - when that user may add comments / attach files in the target project
Bot account Comments with Author = bot, and the first fallback when the original author may not write to the target project. In a service project pair, also the reporter under Customer policy = Bot

When the original author cannot write to the target, the app falls back to the bot account, and then to the app itself. A fallback shows a Bot fallback badge in the sync list - see Troubleshooting for how to react.

Only Jira administrators manage syncs, and each configuration belongs to the administrator who created it - other administrators do not see it.


Forge scopes

The Forge manifest declares everything the recipe needs. You accept the scopes at install time, not per recipe. The scopes the recipe relies on:

Scope What the recipe uses it for
read:jira-work, write:jira-work Read and write issues and comments on both sides of the sync. JSM requests and their comments are Jira issues, so they go through the same scopes
read:project:jira Read project metadata for both sides of the sync
manage:jira-configuration Read project, workflow and field schemas during the pre-flight check (the same scope Studio uses for UI Modification registration)
read:servicedesk-request Read the service desk request-type catalogue when one side of the sync is a JSM project
write:servicedesk-request Create customer requests, transition them, add participants, write request comments (the sync never answers approvals) - added in 5.0
manage:servicedesk-customer Look up JSM customers and organizations - added in 5.0

Writes that need a customer or participant account on the target service desk are performed by the bot account with the JSM permissions you grant it - see Per-project permissions below.

You do not configure scopes per sync - they are app-wide. To check what is granted, open Apps → Manage your apps → JiBrok Studio → Permissions. For the complete list, see the Permissions Reference.


Bot account setup

The bot account is a regular Jira user that the recipe uses for writes when the original actor is unavailable. Use a dedicated service account (for example recipe-bot@your-domain.com) so that bot writes are clearly attributable and its permissions stay minimal.

Pick the bot

  1. In Jira, Settings → User management → Invite users.
  2. Invite a user, for example recipe-bot@your-domain.com.
  3. Set its product access to Jira Software (and Jira Service Management if you sync any JSM project).
  4. Send the invitation, accept, and verify the account can log in.

The bot does not need site admin. Project-level permissions are enough.

Tell the sync about the bot

There is no site-wide default bot: the bot is set per sync configuration, by account ID.

  1. Open Admin Panel → Recipes → Two-project sync, then Edit on the sync.
  2. Set Bot accountId in the Comments section (used for comments and as the attachment fallback).
  3. For a service project pair, set Bot accountId under Customer / Reporter in the Jira Service Management section as well.
  4. Save. A bot account that does not resolve to a Jira user is a validation error and blocks the save.

Account IDs are not exported with a configuration: after an import, re-select the bot and customer accounts before you enable the sync.


Per-project permissions

For each project you sync, the bot and any user whose events should drive the sync need these permissions. Add the bot to a project role with the right grants, or grant them directly to the bot account.

Jira Software / Business project

Permission Why
Browse Projects Read issues and search by JQL
Create Issues Mirror new issues from the other side
Edit Issues Mirror updates
Add Comments Mirror comments
Edit Own Comments Re-edit a comment if the author identity changes mid-sync
Delete Issues Required only if your Deletion policy is Cascade (delete counterpart) - the default is Detach
Transition Issues Required if you sync statuses; the bot performs the transition
Assign Issues Required if assignee is in your field rules
Link Issues Required if Transfer issue links is on, or for Link to the original attachments (see Issue links)

Jira Service Management project

In addition to the above:

Permission Why
Agent access The bot acts as agent for replies and transitions
Service Desk Customer (or matching customer org membership) Required if Customer policy is Original reporter (when possible) or Selected customer
Approve / Decline approvals Not needed - approvers are read-only: differences are audited, approvals are never answered by the sync

If you turn on Sync participants, participants must already exist on the target; unknown accounts are skipped and audited. Sync organizations creates missing organizations on the target and attaches them to its service desk.


Quick permission audit

Before enabling a new sync, click Run pre-flight check in the editor. It re-runs the checks against the live site, for example:

  • Both projects exist and are different, and every field in the rules exists.
  • Every mapped status exists in the target workflow and can be reached by a direct transition.
  • The bot account resolves to a Jira user.
  • Cascade (delete counterpart) is flagged as a warning.

Problems are listed under Issues with this configuration, and the result is shown as Last pre-flight and Pre-flight errors. Save is blocked while any error remains, and a paused sync cannot be resumed until the pre-flight errors are fixed. A missing JSM permission at run time is reported under the JSM scope missing or Permission error category.



JiBrok Studio for Jira Cloud JiBrok Studio for Jira Cloud
Release notes
Core Features
Triggers
Extensions
Data Storage
Scripting Overview
JavaScript Engine
Python Engine
Groovy Engine
Scripting API
Administration
Guides