This flow describes the targeted follow-up between Jira changes and the public Jira area in GitHub Pages.

Purpose

  • maintain the public Jira view in a targeted, traceable way without full syncs

Trigger

  • known Jira or Pages change on an issue

Participating systems

Inputs and outputs

  • Inputs:
    • Jira diff or known Pages change
  • Outputs:
    • updated public Jira area and canonical remote links

Flow

  1. create or resume a journal run
  2. initialize or refresh the local Jira cache
  3. determine the touched keys
  4. update the public Jira area only for these keys
  5. verify remote links and result

Handovers

  • Jira change -> local cache
  • local cache -> targeted Pages update
  • Pages update -> remote link verification

Boundaries and non-goals

  • no unnecessary full sync
  • no second parallel skill for the same flow

Sources