Activating Bug Triage with JIRA
Connecting Jira lets you promote a defect QaaS found into a real Jira issue, and lets the issue’s progress flow back so QaaS can measure how long defects take to detect and resolve.
This is independent of the other two integrations. The Reporter uploads test results, the GitHub App uploads change history, and this one carries defects out to your tracker. Any of them works on its own.
What the app can access
Section titled “What the app can access”The app requests the permissions below. Have them ready for whoever approves apps on your Jira site.
| Permission | Why |
|---|---|
read:jira-work | Read issue status and resolution so QaaS can tell when a defect was fixed. |
write:jira-work | Create the issue when you promote a defect, and keep the link current. |
storage:app | Store the site’s pairing configuration inside Atlassian’s own app storage. |
The app sends data to https://ingest.gamedriver.ai. What leaves Jira is limited to what QaaS needs to match an issue to a defect: the issue key, its status and resolution, its type, and the project it belongs to.
The app does not read your Jira issues generally, does not delete anything, and cannot act on a Jira project until that project has been explicitly paired.
1. Mint a pairing token in QaaS
Section titled “1. Mint a pairing token in QaaS”Sign in to QaaS and open Integrations. On the Jira card, choose the QaaS project you want to connect and generate a pairing token.
The token is shown once, expires shortly after it is issued, and works a single time. Copy it somewhere before moving on. If it expires, generate another. There is no limit, and an unused token costs nothing.
The install link sits with the token on that same panel.
2. Install the app on your Jira site
Section titled “2. Install the app on your Jira site”Open the install link from step 1 and approve the install for your Jira site.
Only a site admin can complete this. If you are not one, send the link to whoever is. Nothing is lost by waiting; generate a fresh token when they are ready, since the first will likely have expired.
Installing the app on its own changes nothing in Jira. The app is inert until a project is paired.
3. Pair a Jira project
Section titled “3. Pair a Jira project”In Jira, open the project you want QaaS defects to land in, then Project settings > QaaS by GameDriver.
Paste the pairing token and save. This binds that one Jira project to the one QaaS project the token was minted for.
To connect a second game, repeat the whole sequence with a new token. One token pairs one project.
4. Tell QaaS what “fixed” looks like
Section titled “4. Tell QaaS what “fixed” looks like”The same settings page asks two questions:
- Which issue type should QaaS create when you promote a defect. Most teams use Bug.
- Which status means the work is done. Usually Done.
The second one matters more than it looks. QaaS uses the issue’s resolution to tell a genuine fix from a “won’t do” or a duplicate, and only a real fix should count toward your resolution times. If your Jira project has a single generic resolution, everything closed will read as fixed. Giving that project a few distinct resolutions is what lets QaaS tell them apart.
5. Promote a defect
Section titled “5. Promote a defect”Back in QaaS, open a defect and promote it. QaaS creates the Jira issue, maps the defect’s severity onto the issue’s priority, tags it so it can be found later, and links the two.
The created issue carries links back to the defect in QaaS and to its change impact, so someone working the ticket in Jira can get to the evidence without being sent hunting.
From then on, status changes in Jira flow back automatically. You do not need to close anything in QaaS by hand.
Who should be allowed to promote
Section titled “Who should be allowed to promote”Promoting creates a real ticket in your tracker, so QaaS treats it as a lead’s decision rather than a tester’s.
Testers can propose a defect, which puts it in the triage queue without touching Jira. QA managers and above get the full disposition dialog, including promote. If a lead is doing the testing themselves, they still get promote directly and are not made to take the two-step route.
Troubleshooting
Section titled “Troubleshooting”The token expired. Expected. It is short-lived on purpose. Generate another from Integrations.
“That token has already been used.” Tokens work once. If you are re-pairing after a change, generate a new one.
No QaaS page appears in Jira project settings. The app is installed on a different site than the one you are looking at, or the install did not complete. A site admin can confirm under the site’s Apps administration.
The install link does not work. Confirm you are signed in to Jira as a site admin. If it still fails, contact GameDriver. Install links are issued by us and can be reissued.
Promoted issues appear in the wrong Jira project. Each pairing binds one Jira project to one QaaS project. Check which QaaS project the token was minted for.
Everything closed counts as fixed. Your Jira project has too few resolutions to distinguish a fix from a rejection. See step 4.
We need to remove a promoted issue from Jira. QaaS deliberately holds no permission to delete Jira issues, so it cannot remove them for you. Delete it in Jira as you would any other issue.