Sanaf AI
Start free
Project Management

Jira, worked by an AI employee

Not another app for your team to learn, and not a set of rules for you to build. You hire an AI employee, you give it access to your Jira account, and you ask it for things in Slack or Teams the way you would ask anyone else on the team. There is nothing to map and nothing to maintain.

  • Project Management
  • Signs in to your account
  • 46 ready-made tools
  • Asked in Slack or Teams
At work

An illustration of how the conversation reads, not a transcript from a client account.

What Jira is

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

You sign in with your own Jira account, the same way you already do. We never see or hold your password.

It can also be told by Jira when something happens, rather than only doing things when you ask.

How a run works

One message in, the work done in Jira.

  1. 01

    You ask

    You message your AI employee in the chat your team already has open, in one sentence, in your own words.

  2. 02

    It works out the step

    It decides what the job needs in Jira. You do not pick anything from a menu or wire anything together.

  3. 03

    It does the work

    Signed in to your own Jira account, inside the access you granted it, doing the thing you asked for.

  4. 04

    It reports back

    It tells you what it did, in the same thread. If it could not do something, it says so rather than guessing.

46 tools it already has

What it can do in Jira

These are the ready-made tools your AI employee already has in Jira. It is not limited to them, but it never has to be taught these.

  • Add AttachmentUploads and attaches a file to a jira issue.
  • Add CommentAdds a comment using atlassian document format (adf) for rich text to an existing jira issue.
  • Add Watcher to IssueAdds a user to an issue's watcher list by account id.
  • Assign IssueAssigns a jira issue to a user, default assignee, or unassigns; supports email/name lookup.
  • Bulk Create IssuesCreates multiple jira issues (up to 50 per call) with full feature support including markdown, assignee resolution, and priority handling.
  • Create IssueCreates a new jira issue (e.g., bug, task, story) in a specified project.
  • Create ProjectCreates a new jira project with required lead, template, and type configuration.
  • Create SprintCreates a new sprint on a jira board with optional start/end dates and goal.
  • Create VersionCreates a new version for releases or milestones in a jira project.
  • Delete CommentDeletes a specific comment from a jira issue using its id and the issue's id/key; requires user permission to delete comments on the issue.
  • Delete IssueDeletes a jira issue by its id or key.
  • Delete VersionDeletes a jira version and optionally reassigns its issues.
  • Delete WorklogDeletes a worklog from a jira issue with estimate adjustment options.
  • Edit IssueUpdates an existing jira issue with field values and operations. supports direct field parameters (summary, description, assignee, priority, etc.) that are merged with the fields p
  • Find UsersSearches for jira users by email, display name, or username to find account ids; essential for assigning issues, adding watchers, and other user-related operations.
  • Get All Issue Type SchemesRetrieves all jira issue type schemes with optional filtering and pagination.
  • Get all projectsRetrieves all visible projects using the modern paginated jira api with server-side filtering and pagination support.
  • Get All UsersRetrieves all users from the jira instance including active, inactive, and other user states with pagination support.
  • Get CommentRetrieves a specific comment by id from a jira issue with optional expansions.
  • Get Current UserRetrieves detailed information about the currently authenticated jira user.
  • Get IssueRetrieves a jira issue by id or key with customizable fields and expansions.
  • Get Issue Link TypesRetrieves all configured issue link types from jira.
  • Get Issue PropertyRetrieves a custom property from a jira issue by key.
  • Get Issue Remote LinksRetrieves links from a jira issue to external resources.
  • Get Issue ResolutionsRetrieves all available issue resolution types from jira.
  • Get Issue StatusesRetrieves all available issue statuses from jira with details.
  • Get Issue Type SchemeGets a jira issue type scheme by id with all associated issue types.
  • Get issue typesRetrieves all jira issue types available to the user using the modern api v3 endpoint; results vary based on 'administer jira' global or 'browse projects' project permissions.
  • Get Issue VotesFetches voting details for a jira issue; requires voting to be enabled in jira's general settings.
  • Get Issue WatchersRetrieves users watching a jira issue for update notifications.
  • Get Issue WorklogsRetrieves worklogs for a jira issue with user permission checks.
  • Get Project VersionsRetrieves all versions for a jira project with optional expansion.
  • Get TransitionsRetrieves available workflow transitions for a jira issue.
  • Get WorklogsRetrieves worklogs for a specified jira issue.
  • Link IssuesLinks two jira issues using a specified link type with optional comment.
  • List BoardsRetrieves paginated jira boards with filtering and sorting options.
  • List Issue CommentsRetrieves paginated comments from a jira issue with optional ordering.
  • List SprintsRetrieves paginated sprints from a jira board with optional state filtering.
  • Move Issues to SprintMoves one or more jira issues to a specified active sprint.
  • Remove Watcher from IssueRemoves a user from an issue's watcher list by account id.
  • Search issuesAdvanced jira issue search supporting structured filters and raw jql.
  • Search Issues Using JQL (GET)Searches for jira issues using jql with pagination and field selection.
  • Search Issues Using JQL (POST)Searches for jira issues using jql via post request for complex queries; ideal for lengthy jql queries that might exceed url character limits
  • Send Notification for IssueSends a customized email notification for a jira issue.
  • Transition IssueTransitions a jira issue to a different workflow state, with support for transition name lookup and user assignment by email.
  • Update CommentUpdates text content or visibility of an existing jira comment.
17 things it can watch for

What Jira can tell it about

It does not only wait to be asked. These are the things Jira can tell your AI employee about the moment they happen, so it can act without anyone noticing first.

  • Comment CreatedA comment is posted on a Jira issue. Can deliver comments on issues the connected account cannot open in Jira itself.
  • Comment DeletedA comment is deleted from a Jira issue. The deleted comment's text still arrives. Can deliver comments on issues the connected account cannot open in Jira itself.
  • Comment UpdatedAn existing comment on a Jira issue is edited. The payload carries the comment as it now reads, not what it said before. Can deliver comments on issues the connected
  • Issue CreatedAn issue is created in Jira, including a sub-task. Can deliver issues the connected account cannot open in Jira itself.
  • Issue DeletedAn issue is deleted from Jira. The deleted issue's full field set still arrives, so the filters below apply to it as usual. Can deliver issues the connected account c
  • Issue UpdatedA field on an existing issue changes — its status, assignee, or anything else on the issue. One edit can change several fields and arrives as one event; creating a su
  • Sprint ClosedA sprint is completed and moves into the closed state.
  • Sprint CreatedA sprint is created on a Jira board. Creating a sprint does not start it — watch Sprint Started for that.
  • Sprint StartedA sprint moves into the active state.
  • Sprint UpdatedA sprint's name, goal, dates or state changes. Starting a sprint also fires this when the same call changed another field; closing one does not.
  • Version CreatedA project version is created in Jira.
  • Version DeletedA project version is deleted outright. A version that disappeared because it was merged into another one fires Version Merged instead.
  • Version MergedA project version is merged into another one, carrying both the version that went away and the one that survived.
  • Version MovedA project version is reordered within its project's release list.
  • Version ReleasedA project version is marked released.
  • Version UnreleasedA released project version is put back to unreleased.
  • Version UpdatedA project version's name, description or dates change. Releasing and un-releasing a version each fire this as well, alongside Version Released and Version Unreleased.
The jobs Sanaf takes in it, and what it does

These are the jobs Sanaf would hold, signed in to your Jira account.

  • AI Project Manager

    Sanaf, on this job

    • Tracks the sprint and flags what will not land
    • Says plainly what will not land this sprint

  • AI IT Support Specialist

    Sanaf, on this job

    • Turns a recurring support problem into a logged issue
    • Adds what customers reported to the issue
Things you could ask, as written

You do not learn a new screen. You type this in Slack or Teams.

  • @Sanaf what will not make this sprint?

  • @Sanaf log the thing that keeps breaking as an issue.

  • @Sanaf summarise what shipped this week for the update.

Access, and who is in charge of it

You stay the boss of your Jira account.

Nothing connects until you approve it. You grant access one app at a time, you can take it back the same way, and everything your AI employee does in there is written down where you can see it.

How we handle your data
  • It signs in to your own Jira account. You are not moving anything into ours.
  • You grant access one app at a time, and you can take it back the same way.
  • Everything it does in Jira is written down, with what it did and when.
  • Anything you tell it to check with you first, it checks with you first.
Other apps in the same corner of the business

It works in Jira and the rest of your software in the same job

A real job rarely stays in one place. Reading a message in one app, checking a record in another and writing the result in a third is one request to your AI employee, not three.

See every app

Questions people ask about Jira

Can an AI employee really work inside Jira?
Yes. It signs in to your own Jira account and works in it the way a new hire would, from the chat your team already has open. Nobody installs anything, and nobody learns a new screen.
Do I have to move anything out of Jira?
No. Nothing moves and nothing is replaced. Your records stay in Jira, your team carries on in the same screens they used yesterday, and your AI employee works alongside them in there.
How does it get into my Jira account?
You sign in with your own Jira account, the same way you already do. We never see or hold your password. You approve it before anything connects, and you can take the access back the same way you gave it.
What can it actually do in Jira?
It has 46 ready-made tools in Jira today, among them Add Attachment, Add Comment and Add Watcher to Issue. The full list is on this page. It is not limited to those, but it never has to be taught them.
Can it use Jira and the rest of my software in the same job?
Yes, and that is usually the point. Reading a message in one app, checking a record in Jira and writing the result somewhere else is one request to your AI employee, not three separate ones you stitch together.
Who decides what it is allowed to do in Jira?
You do. You grant access one app at a time and can withdraw it at any time, anything you ask it to check with you first it checks with you first, and everything it does in Jira is written down with what it did and when.