Jira
Kifas for Jira connects a Jira Cloud site to a Kifas organization so product managers and developers can see, from inside Jira, which engineering work belongs to each product ticket and whether it has shipped. The app is free. Kifas plans and billing are handled at app.kifas.io, never through Atlassian.
What it does
Section titled “What it does”- Link your Jira site to your Kifas organization. Start from either side: click Link to Kifas on the Kifas project page in Jira, or generate a six-digit pairing code in Kifas and enter it on the app’s admin page in Jira. One Jira site links to one Kifas organization.
- Choose which tickets are product tickets and which are dev tickets. Pick projects, issue types and labels from a simple form, or write JQL directly. Each filter can span several projects. A live preview shows how many issues match before you save.
- See linked dev work on every product ticket. The Kifas panel on a product ticket lists the dev tickets and GitHub pull requests that implement it, with the status of each and how the link was found: a Jira issue link, a pull request that mentions the ticket key, or an AI match with a confidence score. Confirm or reject AI matches with one click.
- See a stage on every product ticket. Kifas rolls the linked work up into one of four stages: not started, in progress, code merged, shipped. The stage comes from what actually happened to the code and the dev tickets, not from the product ticket’s own status.
- Get a project overview in Jira. The Kifas project page shows the connection status, lets you map a Jira project to a Kifas project, and shows suite health and recent test runs for that project.
- Work with the same tickets in Kifas. The Tickets page in Kifas mirrors your product and dev tickets with stage, status, assignee, linked dev tickets and pull requests, and updates on its own within a few minutes of a change in Jira or GitHub.
- Unlink at any time. Unlink from the Jira admin page or from Kifas. Unlinking or uninstalling the app removes the mirrored ticket data from Kifas.
Requirements
Section titled “Requirements”- A Kifas account and organization at app.kifas.io.
- Jira Cloud. Jira Data Center and Jira Server are not supported.
- Pull request tracking requires the Kifas GitHub App installed on the repositories you want tracked.
Install
Section titled “Install”- Open Kifas for Jira on the Atlassian Marketplace and click Get it now.
- Choose the Jira site to install it on. You need to be a site admin.
- Review the scopes and confirm.
The app asks for five scopes:
| Scope | Why |
|---|---|
read:jira-work |
Search the issues that match your product and dev filters, read their fields and links, list projects, issue types, labels and statuses for the filter pickers, validate JQL, and check that a viewer can see an issue before showing panel data. |
write:jira-work |
Reserved for creating bug issues in a future release. Not used by any code path today. |
read:app-system-token |
Lets Kifas call the Jira REST API as the app for filter previews and syncs. |
read:app-user-token |
Lets Kifas confirm that the viewing user can see the issue or administer the site before returning panel or admin data. |
report:personal-data |
Report which Atlassian accounts Kifas stores so closed accounts are erased. |
The app runs no code of its own inside Atlassian. Every panel and page is rendered from data held by Kifas at api.kifas.io, and Jira sends issue events to Kifas as they happen.
Link your site
Section titled “Link your site”A Jira site links to exactly one Kifas organization. Until it is linked, the panel and project page in Jira say the site is not linked yet, and the Jira card in Kifas shows Install in Jira and Generate pairing code. You can link from either side.
From Jira
Section titled “From Jira”- In Jira, open any project and click the Kifas tab in the project’s apps.
- Click Link to Kifas. A new tab opens on app.kifas.io.
- Sign in if needed, pick the organization to link, and confirm.
- Kifas returns you to Settings → Integrations → Jira with the message “Jira site linked.” and the site shown as Active.
From Kifas
Section titled “From Kifas”- In Kifas, open Settings → Integrations → Jira and click Generate pairing code. The six-digit code expires in 10 minutes.
- In Jira, open Settings → Apps → Kifas for Jira. You need to be a site admin.
- Enter the code in the pairing field and confirm.
- Both sides now show the site as Active.
If the code does not match, has expired, or you have tried too many times, generate a new one in Kifas and enter it again.
Choose product and dev tickets
Section titled “Choose product and dev tickets”In Settings → Integrations → Jira, the Filters section has two editors: Product tickets and Dev tickets. Each one has a Simple and an Advanced mode.
Simple mode shows chip pickers:
- Projects: one or more Jira projects. Issue types are loaded per selected project.
- Issue types (optional): for example Story for product tickets and Task for dev tickets.
- Labels (optional).
The pickers generate a JQL query, shown under the form. Advanced mode is a JQL text field where you write the query yourself. Save validates the query with Jira and shows Jira’s own error text inline if it does not parse.
Click Preview before saving to see how many issues match and the most recent match. Only issues that match a filter are ever read by Kifas.
The dev filter also has Count as shipped when in: pick the statuses that mean a dev ticket is done. When you leave it empty, any status in Jira’s Done category counts.
Under Matching, turn on Match product and dev tickets with AI if you want Kifas to suggest dev tickets for product tickets that have no Jira link and no pull request mentioning them. Suggestions appear with a confidence score and are never treated as confirmed until you confirm them.
Saving a filter starts a full sync. Within a minute the Tickets page in Kifas lists the matching product tickets.
Read the panel and stages
Section titled “Read the panel and stages”Open a product ticket in Jira. The Kifas panel above Activity shows the ticket’s stage and the work behind it:
- Dev tickets with their current status and assignee.
- Pull requests with their state (open, merged or closed).
- How each link was found: Jira link for a parent, epic, implements or relates link between the two issues, Pull request for a PR whose title or branch mentions the ticket key, or AI with a percentage for a suggested match. AI matches show Confirm and Not related buttons. A rejected match never comes back.
A ticket outside your product filter shows “Not a tracked product ticket.”
Kifas finds pull requests by the issue keys in a PR’s title and branch name, for
example a branch named feat/SCRUM-12-checkout or a PR titled “SCRUM-12 checkout
page”. A PR that mentions a dev ticket is attached to every product ticket that dev
ticket is linked to.
The stage is computed from the linked dev tickets and pull requests:
| Stage | Rule |
|---|---|
| Not started | No linked work, or every linked dev ticket is in the To Do category and no pull request is open or merged. |
| In progress | Anything that is not one of the other three stages. |
| Code merged | There is at least one linked pull request, and every linked pull request that was not closed without merging is merged. Closed, unmerged pull requests are treated as abandoned and ignored. |
| Shipped | Code merged, plus at least one linked dev ticket, and every linked dev ticket is done. “Done” means one of the statuses you picked under Count as shipped when in, or any status in Jira’s Done category when that list is empty. |
Rejected AI matches are left out of the calculation. AI matches you have not confirmed yet are included, but the panel shows them as unconfirmed.
The same stage and links appear on the Tickets page in Kifas. Open a ticket there to see the detail drawer with its dev tickets and pull requests. The page updates on its own as Jira and GitHub change.
Project page
Section titled “Project page”The Kifas tab on a Jira project shows the connection status, a dropdown to map the Jira project to a Kifas project, and, once mapped, suite health and recent test runs for that project with an Open Kifas link.
Data Kifas reads and stores
Section titled “Data Kifas reads and stores”Kifas for Jira is an Atlassian Forge app. It has no backend code of its own inside Atlassian and stores nothing in Atlassian’s Forge storage. Every request the app makes goes to one host, api.kifas.io, operated by Kifas.
What leaves Jira
Section titled “What leaves Jira”Only issues that match the product and dev filters you define in Kifas are read. For each matching issue Kifas receives and stores:
- issue key and issue id
- summary
- description text
- status and status category
- issue type
- priority
- labels
- fix versions
- assignee and reporter: display name and Atlassian account id
- parent issue key
- issue links to other issues (link type and the linked issue key)
- attachment metadata (file name, size, content type) and the Atlassian-hosted attachment URL; attachment contents are not downloaded
- project key
- created and updated timestamps
Kifas also receives Jira issue events (issue created, updated, deleted; issue link created, deleted) so the mirror stays current. Events for issues outside your filters are discarded after the filter check.
When a Jira admin uses the app’s admin page or an individual views a Kifas panel, Kifas receives that person’s Atlassian account id and the site URL, and uses a short-lived user token to confirm that the person can see the issue or administer the site before returning anything.
Where it goes and where it is stored
Section titled “Where it goes and where it is stored”Every request is sent over TLS to api.kifas.io. No other host receives data from the app.
Mirrored ticket data is stored in the Kifas database, hosted on Supabase in the United States. The app is not eligible for Atlassian pinned data residency; app data is stored in the US regardless of the Jira site’s region.
How long it is kept
Section titled “How long it is kept”Mirrored ticket data is removed when the site is unlinked from Kifas (from either side) or when the app is uninstalled from Jira. Removed data is purged permanently within 30 days. Kifas reports the Atlassian account ids it stores to Atlassian’s personal data reporting API every reporting cycle and erases the stored data for any account Atlassian reports as closed.
What is never read
Section titled “What is never read”- Comments
- Worklogs
- Issues outside the product and dev filters you chose
- Atlassian user emails or user directory data (the app does not request
read:jira-user) - Atlassian passwords or API tokens; the pairing code is issued by Kifas, not by Atlassian
Tokens and logs
Section titled “Tokens and logs”Jira delivers a short-lived app token to Kifas with each event and with an hourly heartbeat. Tokens are valid for at most four hours, are stored encrypted at rest with AWS KMS envelope encryption, and are replaced as newer ones arrive. User tokens are used only within the request that delivered them and are never stored. No token is ever written to logs, URLs or code.
Operational logs record installation ids, account ids and job ids. Ticket titles, descriptions and emails are not logged.
Security questions go to security@kifas.io.
What Kifas writes to Jira
Section titled “What Kifas writes to Jira”Kifas writes only as the app (“Kifas”), with the app token Atlassian delivers, and only for an org that linked the site:
- Bugs. When a test fails and Kifas judges it an app bug, a member reviews the draft and submits it, or Kifas files it at once when Bug filing is set to File automatically in Settings → Integrations → Jira. The issue goes to the bug target project and issue type you chose, with the summary
[Kifas] <title>, the labelskifasandkifas-bug, a description with the steps to reproduce, expected and actual behaviour, and links to the run in Kifas. - Attachments. The screenshot of the failing step and, when one exists, the last passing screenshot of the same step. Screenshots over 10 MB are not attached; the description says so. Videos are never attached; the description links to the run page at the failing moment.
- Comments. “Still failing” at most once a day while the bug is open, and “Verified fixed” or “Still failing” after the bug is resolved and Kifas re-runs the test. When the test was suggested from a product ticket, the verification comment also goes on that ticket, and the bug is linked to it with Relates.
- Nothing else. Kifas does not transition, reopen, assign or edit issues it did not create.
Failure evidence
Section titled “Failure evidence”When a test step fails, Kifas saves the screen structure (page HTML on the web, the view hierarchy on Android) and a screenshot of that step, even when step capture is turned off for your org; the screen structure is redacted the same way as step capture in redacted mode. Kifas also keeps the time of the failure in the run video. This evidence is what the failure analysis reads and what a bug links to. It is kept for the same retention period as other run artifacts.
Unlink and uninstall
Section titled “Unlink and uninstall”Unlink from either side:
- In Jira: Settings → Apps → Kifas for Jira → Unlink, then Confirm unlink. You need to be a site admin.
- In Kifas: Settings → Integrations → Jira → Unlink.
After unlinking, the Tickets page in Kifas shows its empty state, the Jira panel and project page report that the site is not linked, and the Jira card in Kifas is back to Install in Jira and Generate pairing code. You can link again at any time from either side.
To remove the app entirely, uninstall it from Settings → Apps → Manage apps in Jira. Uninstalling also removes the mirrored ticket data from Kifas.
Troubleshooting
Section titled “Troubleshooting”The panel says the site is not linked. The Jira site and your Kifas organization are not connected yet, or were unlinked. Follow Link your site. If you linked recently, reload the issue.
A ticket is missing from the Tickets page. The ticket does not match the product or dev filter. Open Settings → Integrations → Jira, click Preview on the filter, and check that the ticket’s project, issue type and labels match. After you change a filter, a full sync runs and the ticket appears within a minute.
A change in Jira takes a few minutes to show up. Jira delivers issue events to Kifas with a delay of up to a few minutes, and the first event for an issue is often the slowest. Changes from GitHub arrive within seconds. Nothing is lost; the panel and the Tickets page update on their own without a reload.
Pull requests are not showing. The Kifas GitHub App needs read access to pull requests and repository contents on the repositories you want tracked. When the app needs re-approval, the Jira card in Kifas shows a banner saying so; accept the permission update in GitHub under Settings → GitHub Apps.
Status or issue type names look translated. Jira translates status and issue type names to the language of the account making the request, and the app’s own account may have a different language from yours. Kifas looks each id up in the site’s catalogs and shows the untranslated name, so a name that still looks translated after the next sync means the site’s language was changed after the catalogs were loaded. It corrects itself on the following sync.
The card says the site is stale. Kifas stopped receiving the hourly heartbeat from this site. Reinstall the app in Jira, or contact support@kifas.io.
Anything else: see Support.