Integrations / Issue tracking
Jira
Assign Jigward the issue. Its status follows the work, and the report lands on the issue.
What Jigward can do in Jira
-
Take an assigned issue as a Task
Assign an issue to Jigward and it becomes a Task in the project's Context, answered with the Task's link and where it stands.
-
Answer a mention
In a comment or in the description, answered in the comment's thread. A mention can also continue the Task, make a choice or stop it.
-
Move the status with the work
While the issue is assigned to Jigward, to in progress and, where the workflow has one, to review.
-
Report on the issue
Reports, questions and the draft pull request as comments, and the files the Task kept as attachments.
-
Create an issue
A Task can create an issue in a project you named for its Context.
-
Catch up on a missed event
Every hour it looks over the issues assigned to its account, so a lost event is still taken in.
How teams use it
-
Assign it the issue
Assign a bug to Jigward as you would to a teammate. It comments with the Task's link and moves the issue to in progress.
-
Ask on the issue
Mention Jigward in a comment to ask about the issue, add detail to its Task, or answer the question it asked.
For example: Is this the same failure as the export bug last week?
-
Review the change where it landed
When the work proposes a change, the issue moves to review with the draft pull request in a comment, and stays there until a person moves it on.
What you need
- A Jira Cloud site, and a Jigward organization with an admin to connect it.
- An Atlassian admin to create a service account for Jigward, and a Jira admin to register a webhook.
Connecting it
- In Atlassian administration, create a service account for Jigward and an OAuth 2.0 credential for it with the scopes below.
- In Jigward, an admin gives the site's address and the credential. Jigward checks them against the site before keeping anything.
- Name each project Jigward works in, with the Context it works in there.
- A Jira admin registers the webhook Jigward shows, with its address and secret.
Security and access
| Permission | Access | Why Jigward needs it |
|---|---|---|
| read:jira-work | Read | To read the issues, comments and projects it works on. |
| write:jira-work | Write | To comment, attach files, move an issue's status and create an issue. |
| read:jira-user | Read | To read the accounts it meets on an issue, such as who wrote a comment. |
Everything Jigward does in Jira it does as the service account you created, so it sees and changes exactly what that account may.
-
An account of its own
Jigward works as its own service account, never as a person and never as an app, and your permission schemes decide what that account can do.
-
Checked before it is kept
The site, the credential and the scopes it grants are checked against Jira first, and the account it will act as is shown.
-
The credential stays encrypted
Kept encrypted under the environment's key and bound to your organization. It is never shown again, never logged, and dropped on disconnect.
-
One site, one organization
A Jira site works for one Jigward organization alone.
-
Signed webhooks
Each delivery's signature is checked with that connection's own secret before the body is read. An admin can rotate the secret at any time.
-
Read back from Jira
What a delivery claims, a comment or an assignment, is read back from Jira before anything is kept.
-
Only assignments and mentions
Other comments are people talking to each other, and Jigward does not take them up.
Jigward never does these in Jira
- Move an issue to done. A person decides that.
- Act as anyone but its own service account.
- Take up a comment that does not mention it.
- Work in a service-management project.
Other integrations
Jira is a trademark of its owner, and naming it does not mean it endorses Jigward.
Meet your next engineering coworker
Bring a question
from your own project.
See how Jigward can help your team understand the system and move the next task forward.
Jigward is in closed testing. Accounts are created by hand; sending a request does not create one.