FAQ & troubleshooting
My custom-field values don’t appear on the Jira issue screen
Section titled “My custom-field values don’t appear on the Jira issue screen”The app stores field values itself and always shows them in its own panels. Mirroring them onto the native Jira issue screen also requires the fields to be added to your project’s screens (Space settings → Screens). On company-managed projects only a Jira admin can do that. Values are never lost — they’re safe in the app either way.
Import returns 401 Unauthorized
Section titled “Import returns 401 Unauthorized”The X-TMF-Token header is missing or doesn’t match. Regenerate the token in the Automation tab and update your CI secret (regenerating invalidates the old one).
Import returns 404 / 409
Section titled “Import returns 404 / 409”404 — the projectKey in the payload doesn’t match a project you can access. 409 — test management isn’t set up for that project yet; run setup first.
A result came back as “unknownKey”
Section titled “A result came back as “unknownKey””No Test Case has that Automation Key. Open the case and set its Automation Key to the exact id your test reports under, then re-run.
A tab says “coming soon”
Section titled “A tab says “coming soon””That capability ships in a later phase — the rest of the app is fully usable meanwhile.
Where is my data stored?
Section titled “Where is my data stored?”Inside your Atlassian site — as Jira issues plus the app’s own Forge storage. The app is Runs on Atlassian eligible and sends no data to external servers.