Bastion Helix for Jira
41 terms

The glossary, in plain English.

The words that come up in Jira reporting, timesheets, project cost, email routing and AI spend — and what Bastion Helix means by each.

A

Actual cost (AC)

What has really been spent on a project so far. In Jira terms, the hours logged, each priced at the rate that applied on the day the work happened.

Adoption band

How regularly a person uses AI tools: none, light, regular or heavy, from the share of their active days on which AI was used. Shown in Workforce Intelligence.

AI-assisted work

A commit or pull request that carries an AI tool’s signature, such as the Co-Authored-By trailer Claude Code adds. Bastion Helix recognises Claude Code, Copilot, Cursor, Codex, Gemini and Devin.

Allow-list (email)

The senders or domains an email channel accepts mail from, for example acme.com and *.acme.com. Blank means anyone. A block list does the opposite.

Atlassian Forge

Atlassian’s platform for building cloud apps whose code runs on Atlassian’s compute and whose data is stored inside Atlassian. Bastion Helix is built entirely on Forge.

B

Billable hours

Logged time that can be charged to a customer. Marking time billable is what turns hours into revenue at a billable rate.

Budget at completion (BAC)

The total budget for a project: the amount everything is measured against in earned value.

Burn

The share of the budget already spent: actual cost divided by budget at completion.

C

Cost performance index (CPI)

Earned value divided by actual cost. Above 1, each dollar spent buys more than a dollar of progress; below 1, less.

Cumulative flow diagram

A chart of how many issues sat in each status over time. Bands that widen show a queue building up.

Cycle time

The time from when work starts on an issue to when it is resolved. Bastion Helix takes the start as the first move out of a To Do-category status.

D

Data egress

Data leaving a system’s boundary — for a Jira app, being sent to servers outside Atlassian. Bastion Helix has none: nothing goes to a server of ours or to a third-party analytics service.

DKIM

DomainKeys Identified Mail: a signature a sending mail server adds, which the receiver can check against the sender’s domain. An email channel can require it.

.drawio file

The file format draw.io saves diagrams in. Bastion Helix imports uncompressed .drawio files and exports to the same format.

E

Earned value (EV)

What the work finished so far is worth, as a share of the budget: percent complete times budget at completion.

Email channel

In Bastion Helix, a connection between a private address and a Jira project: mail forwarded to the address becomes issues and comments in that project.

Email Worker

A Cloudflare Worker that runs when Cloudflare Email Routing receives a message. A few lines of one forward mail to a Bastion Helix channel.

Estimate at completion (EAC)

A forecast of the final cost: budget at completion divided by CPI, which assumes cost performance so far continues. Bastion Helix shows it only after 10% of the budget is spent.

Estimated spend

AI spend worked out from token counts rather than read from a bill — for example Claude Code’s own cost counter. Workforce Intelligence labels it, and replaces it with billed spend when that arrives.

I

Issue key

A Jira issue’s identifier, such as KAN-12. Workforce Intelligence reads issue keys in commit messages, pull request titles and branch names to tie code to issues.

L

Lead time

The time from an issue’s creation to its resolution — how long the person who asked waited.

Locked period

A past stretch of time in which timesheets can no longer be changed, so the hours that went to payroll or invoicing stay as they were.

M

Mail log

Bastion Helix’s record of every message that reached an email channel — including the ones it ignored — and what happened to each, and why.

Managed settings (Claude Code)

A Claude Code settings file an organisation rolls out to everyone, which takes precedence over personal settings. The simplest way to switch on usage telemetry for a team.

O

OpenTelemetry (OTLP)

An open standard for sending metrics, logs and traces. Claude Code reports its usage over OTLP; Workforce Intelligence receives the metrics.

P

Percent complete

How much of a project’s work is done. Bastion Helix takes it from a figure the owner sets, then resolved story points, then resolved issues — never elapsed time.

Pivot table

A table that summarises issues by two fields at once — rows by one, columns by another — with totals, and in Bastion Helix, heatmap cells.

Planned value (PV)

How much of the budget the plan says should have been used by now, based on how much of the scheduled time has passed.

R

Runs on Atlassian

Atlassian’s designation for Forge apps that keep data inside Atlassian. Bastion Helix is built to meet its requirements.

S

Schedule performance index (SPI)

Earned value divided by planned value. Below 1, the project has done less than the plan says it should have by now.

SPF

Sender Policy Framework: a DNS record listing the servers allowed to send mail for a domain. An email channel can check it.

Story points

A team’s relative estimate of an issue’s size. Resolved story points out of the total is one way Bastion Helix measures percent complete.

T

Throughput

How many issues are resolved per week or month.

Time in status

How long issues spend in each workflow status — the fastest way to find where work waits.

To-complete performance index (TCPI)

The cost efficiency needed on the remaining work to finish on budget: (BAC − EV) ÷ (BAC − AC). Above 1 means the rest must go better than it has.

U

Unassigned spend

AI usage from an account or key nobody has been linked to yet. Workforce Intelligence shows it rather than dropping it.

Utilisation

Hours logged as a share of the hours a person had available, after their working schedule and holidays.

V

Variance at completion (VAC)

Budget at completion minus estimate at completion: the forecast overrun (negative) or underrun.

W

Webhook

An HTTPS request one system sends to another when something happens — for example GitHub posting each push.

Web trigger

A Forge feature that gives an app an HTTPS address other systems can post to. Email channels and Workforce Intelligence receive data through web triggers.

Worklog

A Jira record of time spent on an issue: who, when, how long, and a description. Bastion Helix timesheets write ordinary Jira worklogs.

Early access

Be first in when it opens.

One email when early access opens. Nothing else — no newsletter, no drip sequence, and the list isn't shared with anyone.

You're on the list. Talk soon.

Early access members get the first year at launch pricing, locked.
Your address is stored with Resend, the email service that will send that one email.

Recorded from the live demo on this site: the module’s real code running on sample data. Nothing is edited apart from the title cards.