Atlassian (Jira & Confluence) for ticketing
Atlassian's official server covers Jira issues (and Confluence pages), and it is the second of five picks for ticketing. Jira is the most widely used enterprise tracker, so for filing, transitioning, and querying tickets at scale this server reaches a huge installed base. Linear ranks first here for teams that want a faster, lighter ticketing experience; Atlassian takes the next spot on Jira's depth and reach.
For ticketing the draw is direct: an agent can file a bug from a stack trace, triage an incoming request, move it through workflow, and query the backlog with JQL, all against the tracker most large orgs already run.
How Atlassian (Jira & Confluence) fits
The ticketing motions map cleanly to tools. createJiraIssue files a new ticket after getJiraIssueTypeMetaWithFields tells the agent which fields the project and issue type require, editJiraIssue updates it, and getJiraIssue reads it back. Triage and reporting run on searchJiraIssuesUsingJql, the precise query surface for filtering a backlog by status, assignee, or label, while getTransitionsForJiraIssue and transitionJiraIssue advance a ticket through its real workflow. getVisibleJiraProjects and getJiraProjectIssueTypesMetadata orient the agent, and lookupJiraAccountId resolves assignees; getJiraIssueRemoteIssueLinks and getIssueLinkTypes connect related tickets.
The honest trade is weight. Jira's configurability is its strength at enterprise scale and its cost for smaller teams, where Linear's lighter, faster tracker fits better, which is why Linear leads. Asana handles ticketing as general cross-functional work rather than engineering issues. Shortcut is the dev tracker for teams wanting less process than Jira, and Plane is the open-source, self-hostable option. Reach for Atlassian when Jira is your tracker and you need an agent filing, transitioning, and querying tickets with JQL across a large or established setup.
Tools you would use
| Tool | What it does |
|---|---|
| getVisibleJiraProjects | Lists the Jira projects the user can access. |
| getJiraProjectIssueTypesMetadata | Lists the issue types available in a Jira project. |
| getJiraIssueTypeMetaWithFields | Gets the create-field metadata for a project and issue type. |
| getJiraIssue | Retrieves a Jira issue by ID or key. |
| getJiraIssueRemoteIssueLinks | Lists the remote issue links on a Jira issue. |
| getIssueLinkTypes | Lists the available Jira issue link types. |
| getTransitionsForJiraIssue | Lists the available workflow transitions for a Jira issue. |
| lookupJiraAccountId | Finds Jira user account IDs by name or email. |
| searchJiraIssuesUsingJql | Searches Jira issues using a JQL query. |
| createJiraIssue | Creates a new Jira issue. |
FAQ
- How does an agent file and triage tickets in Jira?
- createJiraIssue files a ticket (using fields from getJiraIssueTypeMetaWithFields), searchJiraIssuesUsingJql filters the backlog for triage, and transitionJiraIssue moves a ticket through its workflow, so the full ticketing loop runs through the server.
- Why is Linear ranked ahead of Atlassian for ticketing?
- Linear is faster and lighter, which fits teams wanting less process. Atlassian's Jira is heavier but reaches the largest enterprise base with deep workflows and JQL search, so it ranks second here.
- Can the agent query tickets precisely?
- Yes. searchJiraIssuesUsingJql runs a JQL query, so an agent filters tickets by status, assignee, label, or any field rather than scanning a flat list.