Off the shelf, on the platform side, feeding the Interchange.
Jira. Preview image of sheet A-04, the PNG the sheet build writes beside the PDF, centred on a white frame.
Jira is one source that feeds the Interchange
Jira is off the shelf and known by many teams, and its interfaces are easy to build on. On the platform side it holds the work and its status, and it feeds the Interchange. It is one source among the sources the Interchange reads. It is not the centre.
What flows: an event can open an issue linked to the asset; a person moves the issue to approved; the work order goes to i3; i3's result comes back as an event; a person accepts. Rules in a data file choose each step, and a disabled rule says why.
What is built: a credentials reader and a transport with not-configured, fixture and live modes. It also holds the JSM Assets schema and objects, and issues linked to assets. Webhooks come in and the flows run. Each is tested both ways on a fixture site that answers in Atlassian's published shapes.
State: built and tested on fixtures. No real Jira has been called. The live mode waits for a test project.
Components for Jira
9 components on this site relate to this explainer: 3 document, 2 interchange contract, 1 code and tests, 3 screen. The best 5 are shown.
Picture: Headless capture of poc/index.html?v=wo&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale.
Picture: Headless capture of poc/index.html?v=workflows&m=light, as the proof of concept renders it, 1400 by 875 at 2x scale. Clip: Capture of poc/index.html?v=workflows&m=light, 4 seconds of the screen as it runs, 10 frames a second. No sound.
The Interchange is ours. Jira, off the shelf and used by most teams, feeds it from the platform side, and it carries work to the owner's systems on the other.