Skip to content
FluxGate

Enterprise · Jira and Jev AI

Jira end to end

Moving CHK-142 through In Review, Approved and Done requests, approves and deploys express-checkout in Production, and FluxGate reports each step back on the ticket.

3:53 videoBuilds on:Jira setup

Before you start

  • The Jira integration from Jira setup is ready: the three status rules exist, the alias prod maps to Production, and Production is listed under Jira approves in. The public tunnel is running and the Jira flow FluxGate release is enabled.
  • express-checkout has Development and Staging deployed, and Production shows DEPLOYMENT REJECTED. A rejected stage can be requested again.
  • Sign in as admin System admin and select the team Checkout. Keep Jira next to FluxGate so you can watch both. In Jira, CHK-142 is in To Do and has no labels.

How a ticket drives a release

Three status changes on one ticket take express-checkout to Production. FluxGate acts only on features that are linked to the ticket, and only in the environments the ticket names through its labels.

Jira moves the ticket toThe rule runsWhat happens in FluxGate
In ReviewRequestA pending approval request appears under your approval policy.
ApprovedApproveFluxGate closes the request as approved by Jira. No person votes.
DoneDeployThe approved stage is deployed.

The request is the same approval request a person would create, under the same policy. Jira only starts it. Nothing ships when the ticket reaches Approved: the stage reads DEPLOYMENT APPROVED until the ticket reaches Done.

  1. In FluxGate, open express-checkout from /features. The Overview tab of /features/:id shows the Jira card.
  2. Click Add in the Jira card. Its accessible name is "Add Jira issue".
  3. In Issue key, type CHK-142. In Issue URL (optional), type the address of the ticket. The URL turns the key into a link in the card and on the approval card.
  4. Click Link issue. The card lists CHK-142.
  5. In Jira, open CHK-142 and add the label prod. Type prod in Labels and pick the option prod (New label), or the existing prod. A similar label such as Perf-Test-Prod is a different label and does not map.

Linking needs a system admin or a Team Admin. The label names the environment, and the alias from the setup maps prod to Production. Add the label before the first status change. A ticket with no matching label does nothing.

Linking also writes to Jira. A few seconds after you link, FluxGate can add its web link to the ticket, which lists the current stage of each environment, here with Production as DEPLOYMENT_REJECTED.

Move the ticket

In Review: request

  1. In Jira, move CHK-142 from To Do to In Review.
  2. In FluxGate, the Approvals pill in the header shows a count. Click it to open /approvals. The Pending filter shows a new card with the CHK-142 badge and the reason Jira status 'In Review'. If the card is late, reload the page: the list refreshes every 30 seconds.

Approved: approve

  1. In Jira, move CHK-142 to Approved.
  2. In FluxGate, the card leaves Pending. Click Approved. The card shows the green badge Approved by Jira (CHK-142). If the event carries the Jira user, the display name comes before the key.
  3. Click Details. Under Request context the line Jira status: Approved appears. Votes shows the same Approved by Jira line instead of a vote, and the card counts 0 approvals, because Jira's approval is not a vote.
  4. Open express-checkout at /features/:id and click the Stages tab. Production reads DEPLOYMENT APPROVED.

Done: deploy

  1. In Jira, move CHK-142 to Done. The status list scrolls, so scroll the menu if Done is out of sight.
  2. In FluxGate, reload /features/:id and open Stages. Production reads DEPLOYED. express-checkout is now deployed in all three environments.

What FluxGate writes back

With write-back on, FluxGate comments on the ticket after each event. The comment lists the outcome of every rule that ran. FluxGate also keeps one web link on the ticket and updates it in place. Comments and links are queued and sent by background jobs, so allow up to about 10 seconds.

  1. In Jira, refresh CHK-142. The activity shows comments from FluxGate. The comment for Done reads FluxGate: Jira status 'Done' above express-checkout · Production: deploy applied.
  2. Find the web link titled FluxGate: express-checkout · Development DEPLOYED · Staging DEPLOYED · Production DEPLOYED. Click it. FluxGate opens the flag.

Example timeline

Jira statusFluxGate stage status of ProductionComment FluxGate writes on the ticket
In ReviewDEPLOYMENT_REJECTED to DEPLOYMENT_REQUESTEDFluxGate: Jira status 'In Review' over express-checkout · Production: request applied
ApprovedDEPLOYMENT_REQUESTED to DEPLOYMENT_APPROVEDFluxGate: Jira status 'Approved' over express-checkout · Production: approve applied
DoneDEPLOYMENT_APPROVED to DEPLOYEDFluxGate: Jira status 'Done' over express-checkout · Production: deploy applied

The flow adds exactly three comments and the refreshed web link. Because Jira made these changes, FluxGate adds no second comment for them. The comments come from the Jira user of the API token you gave to write-back. Human actions in FluxGate, such as an approval by a person, get their own comment, for example Approved for Production by <name>.

Audit the run

  1. In FluxGate, click Jira in the Settings group to open /settings/jira. Scroll to the Event log card.
  2. The Events tab lists Done, Approved and In Review for CHK-142, newest first. Each row has the outcome Applied and a stage change such as DEPLOYMENT_APPROVED → DEPLOYED.
  3. Click Outbound. The comment and remote_link jobs read sent.
  4. In Jira, open the flow FluxGate release under Automation and click its audit log. Each run shows Success.

The Events tab keeps 30 days of events. Each row shows the time, the issue, the status, the Jira user when sent, the feature, the environment, the action, the outcome and details. If a rule is refused, the reason is in the details. The Outbound tab lists every comment and link that FluxGate sent. A failed one reads dead and has a Retry button.

Good to know

  • Jira drives FluxGate here. FluxGate never moves your tickets or edits their fields. It only comments and links, and there is no kill switch from Jira.
  • The Approved transition is your Production gate. Limit who can make it in your Jira workflow.
  • Deploy works only on an approved stage. If the ticket jumps to Done before Approved, FluxGate refuses with the reason not approved, changes nothing, and comments express-checkout · Production: deploy refused: not approved.
  • A freeze window still applies. If the stage is frozen, the rule is refused with freeze window <name> and Jira cannot override it.
  • If you link a flag within a minute of earlier activity on it, the ticket can also receive comments for that activity, such as Approved for Staging by sam, with Ref: CHK-142.

Troubleshooting

The ticket moves but nothing happens in FluxGate

Check that the flag is linked to the ticket and that the ticket has the label prod. The Event log says "No rule matched." when no label names an environment. A label that matches no environment is listed as an unknown environment.

Check that write-back is on and Test connection reports connected as <display name>. Look at the Outbound tab. With write-back off it reads "No outbound jobs yet."

Next

Turn on Jev AI assistance and read an AI risk assessment on an approval request in Jev AI assistance.