Create Jira Issues, Publish Confluence Pages And Manage Team Access With Atlassian

If your team runs on Jira and Confluence, a good part of your week is probably spent copying. A customer complaint becomes a ticket by hand, a status report gets retyped into a wiki page, and every new hire means someone working through a list of groups and products to set up. You may be looking for a way to stop doing that. Atlassian makes this work available through APIs, a way for software to talk directly to other software, so your other systems, or an AI assistant, can open tickets, publish pages and manage who has access for you.

What Atlassian does

Atlassian is a software company that develops collaboration, productivity and project management tools. The names you are likely to know are Jira for tracking work and Confluence for team documents, along with Jira Service Management for service desks and Bitbucket for storing software code. Each of those has its own APIs, and all of them are profiled in one place on APIs.io. More on the Atlassian website.

What you can get done

Turn requests into tracked work

Project Management here is Jira’s issue tracking. An issue is one unit of work: a task, a bug or a request. Once software can create issues, the form on your website, the alert from your monitoring tool or the email from a customer can land in the right project without anyone retyping it.

• POST /rest/api/3/issue creates one issue or subtask.
• POST /rest/api/3/issue/bulk creates up to 50 issues in one request, handy for moving a list out of a spreadsheet.
• GET /rest/api/3/issue/createmeta shows which projects and issue types you are allowed to create in.
• PUT /rest/api/3/issue/archive archives up to 1,000 issues by ID or key.
• POST /rest/api/3/issue/archive archives up to 100,000 issues matching a search, for when an old project needs clearing out.

Control who has access

Identity & Access Management is about joiners and leavers. Connect it to your HR process and new starters arrive with the right access, while people who leave lose it the same day instead of whenever someone remembers.

• GET /v1/orgs/{orgId}/users lists the accounts your organization manages.
• POST /v2/orgs/{orgId}/users/invite invites people to your organization.
• DELETE /v2/orgs/{orgId}/directories/{directoryId}/users/{accountId} removes someone from a directory.
• GET /v2/orgs/{orgId}/directories/{directoryId}/users/count gives you a headcount without listing everyone.
• GET /v1/orgs/{orgId}/groups lists the groups in your organization.

See whether your software builds are healthy

Continuous Integration Management covers Bitbucket Pipelines, which automatically build and test code when it changes. If you manage developers rather than being one, this is what lets a dashboard answer “did that pass?” without interrupting anybody.

• GET /repositories/{workspace}/{repo_slug}/pipelines lists the pipeline runs for a code repository.
• POST /repositories/{workspace}/{repo_slug}/pipelines starts a new run.
• GET /repositories/{workspace}/{repo_slug}/commit/{commit}/statuses shows the build results for one change.

Follow your releases

Software Release & Deployment Management tracks what went out and who holds the keys. A deploy key is a credential that gives a machine access to one repository, which makes it worth auditing.

• GET /repositories/{workspace}/{repo_slug}/deployments shows the deployment history of a repository.
• GET /repositories/{workspace}/{repo_slug}/deploy-keys lists the deploy keys with access to a repository.
• DELETE /repositories/{workspace}/{repo_slug}/deploy-keys/{key_id} revokes one right away.

Tell your other systems when something happens

Webhook & Event Subscription Management sets up webhooks, messages Atlassian sends to a web address of yours when an event happens across a Bitbucket workspace.

• GET /workspaces/{workspace}/hooks lists the webhooks installed on a workspace.
• POST /workspaces/{workspace}/hooks creates one.
• DELETE /workspaces/{workspace}/hooks/{uid} stops one for good.

Workflows that put it together

A workflow is a recipe of several calls in order that finishes a real job. APIs.io catalogs 17 for Atlassian, including:

• Jira Create and Assign Issue creates an issue, assigns it to someone and confirms the assignment.
• Jira Create Issue and Transition creates an issue and moves it to a new status.
• Jira Create Project and First Issue stands up a new project and seeds it with its first issue.
• Confluence Create and Update Page creates a page, reads its version and publishes an updated body.
• Confluence Create Child Page confirms a parent page and creates a new page under it.
• Confluence Create Page with Label creates a page and tags it so it can be found later.

Ask for it in plain language

Our conversational overlay for Atlassian maps everyday questions to the operation that answers them, so an AI assistant knows which call to make. These are the kinds of things you can ask:

• “Can I create many Jira issues in a single request?”
• “Can I archive every issue that matches a JQL search in one go?”
• “Can I invite several people to my organization by email at once?”
• “Did CI pass on this commit?”
• “How do I revoke a deploy key’s access to one repository?”
• “How do I get notified of events from every repository in a workspace?”

You can see one in the Atlassian Analytics phrasing overlay.

Getting started

Atlassian has a free tier with self-serve signup, and you call its hosted service. The Jira Software reference is a good place to begin: read about the backlog, boards and epics. On APIs.io, see the Atlassian profile, the Jira Software Board API, the Jira Software Sprint API and the Jira Service Management Customer API. Pick the one ticket your team retypes most often and automate that first.