Docs

Integrations / Ticketing / Jira

Add Participant to Work Item

Add a person as a request participant on a Jira Service Management work item from a runbook

Adds a person as a request participant on a Jira Service Management work item. A participant sees the request in the customer portal and receives its notifications, so this is how a runbook brings a manager, an approver, or an affected colleague into a request without giving them a Jira license.

How It Works

  1. The agent gives the tool a participant: an email address, a Risotto identity ID, or an Atlassian account ID.
  2. The agent may also give a work item key, for example ITSD-123. With no key, Risotto uses the work item the current ticket is linked to. That link exists when the ticket's department syncs to Jira.
  3. Risotto resolves the participant to an Atlassian account, the same way Get Atlassian User ID does.
  4. When the email address matches no Jira account, Risotto checks the work item's service desk for a portal-only customer with that address, because Jira's user search does not return one.
  5. Risotto adds the resolved account to the work item as a request participant.

Authentication

This tool runs on your organization's Jira connection, the same connection the ticket sync uses. There are no credentials to enter on the tool itself.

Connect Jira under Settings → Integrations first. See the Jira integration guide.

Configuration Options

  • Create JSM customer if missing (off by default) - When the participant's email address has no Atlassian account, create a portal-only customer on the work item's service desk and add that customer. Leave it off to have the tool report the missing account instead.

Example Runbook Uses

  • Add the requestor's manager to an approval request so they can follow it in the portal
  • Add an application owner to an access request for their app
  • Add a colleague named in a shared incident to the work item that tracks it

Limitations

  • Jira Service Management only. The key must name a customer request, not a plain Jira issue.
  • With no work item key, the tool needs the current ticket to be linked to a Jira work item through its department's Jira sync. A ticket that syncs to another system has no key to fall back on.
  • The tool adds participants. It does not remove them.

Troubleshooting

No Atlassian account with the email address was found in Jira

The address matches no Jira account and no portal customer on that service desk. Check the address, or turn on Create JSM customer if missing to have Risotto add a portal-only customer.

Jira rejected adding the participant

Confirm the key names a Jira Service Management request, and that the Risotto app is allowed to manage participants on that project.

No work item key was given and the current ticket is not linked

Add a Jira ticket sync to the ticket's department (Settings > <department> > Ticket Sync > Add ticket sync), or have the runbook pass the work item key.

Something wrong or missing? Report an issue · View as Markdown