Skip to content
Ben Dangelmayr
Jira board, close-up: two issues carry the same invoice number INV-1001 and are linked by a red marker reading INV-1001 · 2×.
Ship External ID Guard: one invoice number in two Jira issues

All work

Ten Jira Cloud apps on Atlassian Forge

I build small Jira Cloud apps on Atlassian Forge outside my day job and publish them under the Dangel Studio name, from product idea to support. The first went live in August 2026.

Role
Sole developer and publisher
Built with
Atlassian Forge, coding agents
Status
10 apps listed, October 22, 2026

Product scene: three apps on one Jira board

  1. Issues move across a Jira board, the way they do on any working day.

  2. Docs: External ID Guard

    A scan finds two issues that carry the same invoice number, INV-1001.

  3. Docs: Stale Radar

    The threshold steps through the app’s 60, 30 and 14 day settings, and older issues are marked.

  4. Docs: Automation Heartbeat

    A canary issue that should be updated every day goes without an update, and the interval is marked overdue.

Swipe sideways to see the whole board.

Still from the scene: a Jira board in which two issues with the invoice number INV-1001 are linked
Sample data, drawn live from my own code.

The apps

Each app covers one narrow Jira workflow. Its name links to the documentation.

  • Requirement Drift Guard Catch requirement changes after work has started.
  • Reopen Receipt Track every reopened issue, record the reason, and turn rework into retro data.
  • Weekly Brief A deterministic weekly status per project: done, started, new, overdue and due soon, plus copy-ready Markdown.
  • Tree Clone Clone an epic with its issues and subtasks: one click, a report of created, failed and not attempted issues.
  • External ID Guard Catch duplicate invoice numbers, ticket ids and contract references before they cause double work.
  • Stale Radar Find issues nobody touched for a while, grouped by assignee; every snooze and exemption with an optional reason.
  • Automation Heartbeat Automation rules fail silently. A canary issue makes the silence visible.
  • Field Health A live completeness score for the fields your process actually needs, plus the exact issues to fix.
  • Handoff Receipt Who held this issue, how long, and in which status it changed hands, straight from the issue history.
  • Rollup Guard Epic progress and hierarchy mismatches at a glance, no Premium plans required.

Tests and permissions

All numbers in this section come from one measurement run across the ten apps on August 31, 2026.

  • Tests: 158 automated test cases in 18 test files; on the re-run all ten suites passed.
  • Core logic: runs without Jira and is tested separately from the interface; five apps also test their Jira-facing layer against stubbed Forge APIs.
  • Permissions: nine of ten apps request no write access (exception: Tree Clone, which exists to create issues); no app requests more than two; no manifest declares an external domain.
  • Review: a 13-stage module from market research to post-release review, with 83 tests of its own.
  • Sign-off: the approval stage rejects agent identifiers, including disguised Cyrillic spellings; a second model review must come from a different model family.

Sabotage probe: a fault the tests missed

I introduced a deliberate fault in Tree Clone. The tests stayed green because the test data was already sorted. After I changed the test data, the same fault was detected in three places.

All apps with documentation · Vendor page on the Atlassian Marketplace