The problem it solves
Shipping decisions are scattered across a Jira issue's fields, comments, children, and (when visible) pull requests and checks. People waste time reconstructing "can we ship this?" and sometimes treat a missing field as an empty one. ShipContext answers that question in the issue itself, and says "Can't see …" when a field cannot be read.
What it does
ShipContext is an Atlassian Forge app (version 2.1.0) for software teams. On a Jira work item it shows:
- A deterministic Ship or Wait recommendation and one next step.
- What's already decided, who is responsible, and which blockers are still open.
- Honest "Can't see …" lines instead of pretending unread fields are empty.
It is installed on the official free Forge demo site (Distribution: Sharing, Jira only). Teamwork Graph and Rovo are not in this version and are not claimed. Marketplace listing is not part of this entry. Do not start a paid plan.
How we built it
The app uses Forge UI Kit with jira:issueContext and jira:issuePanel, and read-only Jira scopes read:jira-work and read:jira-user. Recommendation logic is deterministic from the fields the app can actually read. A public privacy page is served by a Cloudflare Worker at https://shipcontext-privacy.getbilltrack.workers.dev/ . Local tests (npm test) and forge lint were clean on the 2.1.0 tree. Judges install the same distribution link that is already in the README; that URL must stay unchanged.
Challenges we ran into
The free Forge demo site cannot always see pull requests or CI checks, so the live panel must say "Can't see …" rather than invent a green status. Recording a truthful official video of the live install (MSD-13), then a clearly labeled canned Demo scenario (SHIP-42), took more care than a single local mock would have. Secrets (Forge API token, .env, .forge/) stay off the public tree.
Accomplishments that we're proud of
A working 2.1.0 install on the official free Forge demo site, a 4-minute-50-second official video under the 5-minute limit, a public privacy page, and a judges' installation link that has not been altered. The panel's recommendation on live MSD-13 is Ship, with honest gaps; the SHIP-42 demo scenario shows Wait, including failed CI and an open sub-task.
What we learned
A shipping recommendation is only useful if missing data is visible as missing. "Can't see …" is more honest, and more useful to a judge, than a confident empty list.
What's next
No paid Forge plan is planned. Graph and Rovo are intentionally not claimed in 2.1.0. A later version could add them only if they are actually implemented and the official scopes and regions allow it.
Built With
- atlassian-forge
- atlassian-jira
- cloudflare-workers
- javascript
- react
- ui-kit
