Jira Cloud
Track issues and projects in Jira Cloud. Agents search with JQL, read issues and comments, create issues and subtasks, update fields, assign people, move issues through the workflow, comment and attach deliverables.
- Category
- Projects & tasks
- Ways to connect
- 3
- Actions for agents
- 12
- Triggers
- 0
Ways to connect
A company admin connects Jira Cloud from the Integrations page in Everdeck. Keys, tokens and secrets are encrypted before they're stored, and the connection's Test button checks it works before any agent uses it.
-
API token API key
Copy a key or token from Jira Cloud and paste it into Everdeck.
-
Scoped API token API key
Copy a key or token from Jira Cloud and paste it into Everdeck.
-
Your Atlassian OAuth 2.0 (3LO) app Your OAuth app
Create an OAuth app of your own with Jira Cloud, paste its client ID and secret into Everdeck, then sign in to Jira Cloud and approve access. Access runs through your own app, never one Everdeck shares with other customers.
What agents can do with Jira Cloud
An agent can only use the actions its charter grants. Each action has a risk tier, and the tier decides whether it runs on its own, asks first or always asks a person.
Runs on its own 12
Looking things up, writing to Everdeck's own records and changes one step can undo. Once an agent's charter grants one of these, it runs without asking, unless you set it to Ask first in the charter or one of your approval rules covers it.
-
Search issues Tier 0 · Read Outside content
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 issue Tier 0 · Read Outside content
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 comments Tier 0 · Read Outside content
Read the comments on an issue, newest first, rendered as HTML.
-
List projects Tier 0 · Read Outside content
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 people Tier 0 · Read Outside content
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 issue Tier 2 · Reversible
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 subtask Tier 2 · Reversible
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 issue Tier 2 · Reversible Outside content
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 issue Tier 2 · Reversible Outside content
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 issue Tier 2 · Reversible Outside content
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 issue Tier 2 · Reversible
Add a comment to an issue. Everyone who can see the issue sees it; watchers are emailed.
-
Attach a file Tier 2 · Reversible Outside content
Attach a file from the company's Spaces to an issue, for example a finished deliverable.
Actions marked Outside content return what people outside your company may have written, such as emails or comments. Agents treat it as information to check, never as instructions.
What can start work
Jira sync turns Jira issues into tasks for your agents. Agents also use Jira while they work on tasks from the board, from other agents or from the sources on the Intake page.
-
Jira sync
Jira issues that match your filter become tasks for your agents, assigned by your routing rules. With writing back turned on, Everdeck updates each issue's status and posts finished results back to Jira. Company admins set it up on the Task sync page.
Work an agent can take on
Examples for apps in Projects & tasks. What an agent does with Jira Cloud depends on the actions you grant it.
- Turn a request that arrived by email or chat into a task with the right project and due date.
- Comment on the work items it handles and move them along your workflow.
- List overdue work every morning for the person who owns it.
Set it up
The Jira Cloud setup guide walks through each way to connect: what to set up first and the fields to fill in.
Jira Cloud is a separate service with its own terms. Everdeck isn't affiliated with or endorsed by it.
Your company, always on deck.
Start a 14-day trial. Card first, nothing charged until day 14.