Who can connect Jira for the company?

A company connection is installed by an administrator.

Can I connect Jira just for myself?

Anyone can install a personal connection within the plan’s limit and use it in their own conversations.

Do I use my Jira account or a company account?

Yours, either way: sign-in to the Jira account or an API key generated in your account. In both cases the credential is yours and stays encrypted.

Does Skyller do everything on that action list?

The list is what the vendor offers. What the AI uses in your company is what the administrator turned on, for the groups they defined — Skyller never widens the connector's access.

Does an action in Jira happen without anyone approving it?

Reads happen within permission. Write actions have a risk level; sensitive ones show a confirmation card before running and are recorded. The company adjusts the classification when needed.

Jira does not show up in my company's catalog.

The administrator may have hidden the integration for your company, or the vendor may have discontinued it — in that case it leaves the catalog on the next synchronization, without deleting what was already connected. Talk to whoever administers Skyller in your company.

Integration · Projects and tasks

Jira in Skyller.

Follow tickets and open items without opening one more management screen. Below, the actions and events the vendor publishes, what it takes to start and where this fits into the work.

Try it free Book a demo

Actions and events

Jira

Projects and tasks

A tool for bug tracking, issue tracking, and agile project management.

Actions: 97
Events: 17

Source: Composio catalog
Login: Sign-in or API key
Country: Global — no specific country
Actions list: re-read from the vendor every 24 hours
Official site: www.atlassian.com/software/jira

Description and action names are the ones the vendor publishes, in English; action descriptions are shown summarized. Skyller does not alter that content.

97 ACTIONS

published by the vendor; the company enables only the necessary ones

17 EVENTS

triggers the system can send, when the vendor offers them

SIGN-IN OR API KEY

each person signs in with their own credential, encrypted

APPROVAL BY RISK

sensitive actions show a card before running

Live proof

One request, two real Jira actions and one approval.

The scene uses actions the vendor publishes for Jira. In your company, only the functions turned on by the administrator come into play.

Input
A team member asks, in the conversation, for something that today requires opening Jira — inside their area's space, with their login.
What Skyller does
1. 01Picks, among the enabled functions, the action “Get Issue” and queries Jira with the person's own credential.
2. 02If the request requires writing — for example, “Add Comment” —, shows the card with what it is about to do and waits for Approve.
3. 03Returns the result in the conversation and records who asked, which action was used and when.
Result
Jira stops being an open tab and starts answering inside the conversation — through the functions your company enabled.

What this scene does not promise

Both actions come from the vendor's catalog; in your company only the functions turned on by the administrator are available.
If a write action is not classified as sensitive, it may run without a card; the classification is adjustable by the company.
Being in this catalog does not mean being installed, with a valid login, working in your company.

Illustrative scene with fictitious data; the actions mentioned exist in the vendor's catalog.

Where this helps your work

Jira inside the conversation where the work happens.

Three common situations for people who use Jira every day. What Skyller does in each one depends on the functions your company turns on.

Tracking progress

“What is overdue in the customer's project?”

The coordinator asks and Skyller lists the overdue tasks in Jira, with her login, within the projects she can see.

Progress without opening the board

Distributing the work

“Create the review task and assign it to Carla.”

Creating and assigning is a write action: Skyller shows the card with title, assignee and due date and creates it in Jira after Approve.

Task created with approval

Administering

“Creating a task is fine; deleting a project is not.”

The administrator turns on only what the team needs in Jira and restricts it to groups. The record shows who created what through the conversation.

Only the enabled functions

Actions and events

What the vendor offers in Jira.

Names as the vendor publishes them, in English, with the description summarized to its first sentence. In your company, the administrator turns on only the necessary actions; none of them runs without permission, and sensitive ones go through approval.

Showing 12 of 97

Add Attachment
JIRA_ADD_ATTACHMENT
Uploads and attaches a file to a Jira issue.
Add Comment
JIRA_ADD_COMMENT
Adds a comment using Atlassian Document Format (ADF) for rich text to an existing Jira issue.
Add Users to Project Role
JIRA_ADD_USERS_TO_PROJECT_ROLE
Adds users and optionally groups to a project role.
Add User to Group
JIRA_ADD_USER_TO_GROUP
Adds a user to a Jira group.
Add Watcher to Issue
JIRA_ADD_WATCHER_TO_ISSUE
Adds a user to an issue's watcher list by account ID. Requires the authenticated user to have permission to view the issue and manage watchers; insufficient permissions may result in silent failure or an error response.
Add Worklog
JIRA_ADD_WORKLOG
Tool to add a worklog entry to a Jira issue. Use when logging time spent on an issue.
Analyse Jira Expression
JIRA_ANALYSE_EXPRESSION
Analyses Jira expressions for syntax validation, type checking, and complexity analysis. Use when you need to validate Jira expression syntax before using it in automation rules, custom fields, or workflows.
Assign Issue
JIRA_ASSIGN_ISSUE
Assigns a Jira issue to a user, default assignee, or unassigns; supports email/name lookup.
Bulk Create Issues
JIRA_BULK_CREATE_ISSUE
Creates multiple Jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
Check User Permissions
JIRA_CHECK_PERMISSIONS
Check user permissions for global and project-level operations in Jira. Use this action to verify whether a user has specific permissions at the system level or within projects.
Create Board
JIRA_CREATE_BOARD
Creates a new Jira board (kanban, scrum, or agility) with optional filter and location configuration. Use this action when you need to set up a new board for a project or create a personal board for tracking work.
Create Group
JIRA_CREATE_GROUP
Creates a new group in Jira with the specified name.

Before you start

What your company needs to use Jira.

Login: Sign-in to the Jira account or an API key, depending on what your account in the service allows. Either way the credential belongs to the person and is encrypted.
Who installs: An administrator connects Jira for the company and shares it with people or groups. Anyone can connect just for themselves, within the plan's limit.
Functions: 97 published actions: the administrator turns on only the necessary ones. Sensitive ones ask for confirmation before running.
Plan: Counts as a company or personal connection within the plan's allowance; the larger plans have no cap. The connections-per-plan table is on the catalog page.

Questions from the people who decide