Jira
The Jira integration links your feature flags to Jira issues and surfaces each flag's status and per-environment variations directly in the issue's Development panel in Jira — so engineers see flag state without leaving their ticket.
The Jira integration is available on the Enterprise plan only.
How it works
RedPennon ships a single Atlassian Forge app that you install from the Atlassian Marketplace. Once the app is installed and linked to your RedPennon organisation, RedPennon pushes flag data into Jira's Development panel using Atlassian's Jira Software Feature Flags API.
For each linked issue, Jira's Development panel shows:
- The flag name, its current status (enabled/disabled), and a link back to RedPennon.
- One row per environment: the environment name, its type (production, testing, or development), and the variation currently served there.
The data is pushed automatically whenever:
- A Jira ticket ID is added to or removed from a flag.
- A flag's status changes (for example development → live → complete → archived).
- The variation served in an environment changes.
Connecting your Atlassian site
You must be an organisation owner or admin to set this up. There are no API keys or OAuth credentials to manage — you install the app and link it with a one-time code.
- Install the app. From the Atlassian Marketplace, find RedPennon Feature Flags and install it into your Jira site.
- Generate a linking code. In RedPennon, go to Settings → Integrations → Jira and select Generate linking code. The code is valid for 30 minutes.
- Link your site. In Jira, open Apps → RedPennon Feature Flags → Setup, paste the linking code, and select Link this site.
Once linked, the Jira sub-tab in RedPennon shows your connected site. You can Unlink at any time; existing ticket links on your flags are preserved but no further updates are pushed until you re-link. Uninstalling the app from Jira also stops updates.
Optional: per-project Jira project filter
On the Jira sub-tab, each of your RedPennon projects can be mapped to a specific Jira project. This is optional and is used to scope which Jira project a project's flags relate to.
Linking Jira tickets to a flag
You need publisher permission to edit a flag's ticket links (the same permission required to edit tags).
- When creating a flag: enter Jira ticket IDs (for example
WEB-123) in the Jira Ticket field on the create dialog. Type a key and press comma or Enter to add it as a chip. - On an existing flag: open the flag's Manage settings and edit the Connected Jira ticket IDs field the same way.
Ticket IDs are validated against the standard Jira key format (for example WEB-123) and are upper-cased automatically. Removing a chip unlinks that issue.
Linked tickets appear as pills on the flag's Overview page, each linking through to the issue in Jira.
What gets updated and when
| Event | Effect in Jira |
|---|---|
| Add a ticket ID to a flag | Flag data appears in that issue's Development panel |
| Remove a ticket ID | Flag data is removed from that issue |
| Flag status change | Status updates on every linked issue |
| Environment variation change | The environment row updates on every linked issue |
Issue summary, status, and type shown in RedPennon are refreshed on a nightly schedule.