Jira Cloud setup guide

Agents keep projects moving: they read, create and update tasks and issues where your team works.

To put Jira Cloud to work after connecting it, see Jira sync.

Ways to connect

Company admins connect apps, on the Integrations page in Everdeck: open Jira Cloud, choose one of the ways below, follow its steps and fill in its fields. Everdeck checks what you enter before it saves anything, and asks you to confirm it’s you (your second factor) before you type any secret. How connecting works.

Jira Cloud can be connected 3 ways. Where there’s a key or token to paste, that’s usually the quickest.

API token

API key.

1. Sign in as the Atlassian account the agent should act as (a dedicated account keeps its work easy to spot).
2. Open https://id.atlassian.com/manage-profile/security/api-tokens and choose Create API token (not "with scopes"). Pick an expiry of up to one year.
3. Paste your site URL, the account email and the token into the form.

Field	What to enter
Site URL	Web address. For example https://your-team.atlassian.net.
Atlassian account email	Email address.
API token	A secret: Everdeck saves it encrypted and never shows it again. Where to find it.

Disconnecting deletes the credentials Everdeck saved, but Everdeck can't revoke them: the key, token or password itself keeps working at Jira Cloud until you delete or rotate it there.

Scoped API token

API key.

1. Open https://id.atlassian.com/manage-profile/security/api-tokens and choose Create API token with scopes.
2. Pick Jira as the app and select the scopes read:jira-work, write:jira-work and read:jira-user. Pick an expiry of up to one year.
3. Paste your site URL, the account email and the token into the form. We look up the site's cloud id for you.

Field	What to enter
Site URL	Web address. For example https://your-team.atlassian.net.
Atlassian account email	Email address.
Scoped API token	A secret: Everdeck saves it encrypted and never shows it again. Where to find it.

Disconnecting deletes the credentials Everdeck saved, but Everdeck can't revoke them: the key, token or password itself keeps working at Jira Cloud until you delete or rotate it there.

Your Atlassian OAuth 2.0 (3LO) app

Your OAuth app.

This way signs in with an OAuth app you create for Jira Cloud, as its steps describe: Everdeck never uses an app of its own. Register this redirect URI with your app:

https://everdeck.io/api/oauth/callback

Then save the app’s client ID and secret in Everdeck, on the connect page or under OAuth apps, and sign in.

1. Open https://developer.atlassian.com/console/myapps, choose Create > OAuth 2.0 integration and name it.
2. Under Authorization, configure OAuth 2.0 (3LO) and enter the callback URL https://everdeck.io/api/oauth/callback.
3. Under Permissions, add the Jira API and select the scopes read:jira-work, write:jira-work, read:jira-user and manage:jira-webhook.
4. The app is private by default, so only its owner can connect it. To connect with a different Atlassian account, turn on sharing under Distribution first.
5. Under Settings, copy the Client ID and Secret into the form, then approve access to your Jira site.

Field	What to enter
Site URL (optional)	Text. For example https://your-team.atlassian.net. Only needed when your Atlassian account can reach more than one site: the site to connect.

The scopes Everdeck asks for:

• read:jira-work
• write:jira-work
• read:jira-user
• manage:jira-webhook
• offline_access

Disconnecting deletes the tokens Everdeck saved. Remove Everdeck under Connected apps in the person's Atlassian account settings.

What agents can do

An agent uses an action only when its charter grants it, on the agent’s Tools tab, where you choose whether each one runs by itself (Auto), asks first or never runs. Each action has a risk tier: tier 3 actions, which customers or the public see, ask first unless you choose otherwise, and tier 4 actions (money, deleting things, access) always need a person. How tools and tiers work.

Actions marked Reads outside content return things people outside your company may have written. Agents treat what they read as information, never as instructions, and their riskier actions later in the same session need approval.

• Search issuesTier 0 · ReadReads outside contentjira_search_issues

  Find issues with JQL. Returns key, summary, status, assignee, priority, type and last update. The JQL must contain at least one restriction (for example a project or assignee). Pass next_page_token from the previous result to read the next page.

• Read an issueTier 0 · ReadReads outside contentjira_get_issue

  Read one issue: summary, description (as HTML), status, assignee, reporter, priority, labels, due date, parent, and the workflow transitions you can make from its current status.

• Read commentsTier 0 · ReadReads outside contentjira_list_comments

  Read the comments on an issue, newest first, rendered as HTML.

• List projectsTier 0 · ReadReads outside contentjira_list_projects

  List projects you can see, optionally filtered by name or key, with each project's issue types (use these names in create_issue and create_subtask).

• Find peopleTier 0 · ReadReads outside contentjira_find_users

  Find active users by name or email prefix. Returns the accountId needed to assign issues. Email addresses are hidden for people whose profile visibility does not allow it.

• Create an issueTier 2 · Reversiblejira_create_issue

  Create an issue in a project. Use list_projects for the project key and issue type names. Set labels, priority or a due date afterwards with update_issue, and the assignee with assign_issue.

• Create a subtaskTier 2 · Reversiblejira_create_subtask

  Create a subtask under an existing issue. The issue type must be the project's subtask type (often "Subtask" or "Sub-task"; list_projects shows it with subtask true).

• Update an issueTier 2 · ReversibleReads outside contentjira_update_issue

  Change an issue's fields. Send only the fields to change. Watchers are emailed about the change. To change the status use transition_issue; to change the assignee use assign_issue.

• Assign an issueTier 2 · ReversibleReads outside contentjira_assign_issue

  Assign an issue to a person by accountId (from find_users or get_issue). Use "-1" for the project's default assignee. The new assignee is notified.

• Move an issueTier 2 · ReversibleReads outside contentjira_transition_issue

  Move an issue to another status by performing a workflow transition. Call get_issue first: it lists the transitions available from the current status with their ids.

• Comment on an issueTier 2 · Reversiblejira_add_comment

  Add a comment to an issue. Everyone who can see the issue sees it; watchers are emailed.

• Attach a fileTier 2 · ReversibleReads outside contentjira_add_attachment

  Attach a file from the company's Spaces to an issue, for example a finished deliverable.

Testing, problems and disconnecting

Everdeck checks the connection when you save it. On the connection’s page in Integrations, Test checks it again at any time.

If Jira Cloud later refuses the connection, for example because a key was deleted or a sign-in expired, the connection shows Needs attention on the Integrations page and the people who manage connections are told. Agents can’t use it until a company admin fixes it with Edit or Reconnect.

To stop agents using Jira Cloud, open the connection and select Disconnect. Agents stop using it at once and its saved credentials are deleted. What else happens depends on how it was connected: each way above says.