...
There is no synchronization between Jira and GitHub: changes on either side are not transmitted across.
Expand | ||
---|---|---|
| ||
Below here is the content of the page from November 2022: Integration SpecMVP - Linked functionality onlyFeatures
Constraints
Questions to Answer(BTW: “and vice-versa” throughout)
Use CasesLinked: 1 GH Issue → many Jira tickets
Example: Jira tickets as action items from GitHub issuesConvenience utility for creating tickets in Jira to track work for reviewing OSPRs & provide advance notice for internal workstream interruptions. The status of a ticket may be tracked in GitHub until it requires the attention of the maintaining team (at which point a "review X PR" ticket can be created in Jira) or the maintaining team can use these tickets to plan ahead (e.g. make multiple review or technical discovery tickets and plan cycles for blended or FC projects). Flows
Linked & Synced: 1 Jira ticket → 1 GH Issue
Example: Parallel tracking for Epic ticketsProvide visibility for community into larger feature development work being done by the maintaining team. This is primarily for conveying status and providing a comprehensive technical roadmap for a given software component. Should link to wiki pages / approach docs for more substantive description and use standard conversation channels (e.g. Discourse & Slack) for discussion. Example: Parallel tracking for Bugs & Technical tasksProvide visibility for community around longer term technical roadmap tasks (e.g. support Tutor, upgrade Node) along with insight into how the maintaining team is prioritizing these tickets. Provides transparency around known issues that are not being worked on (e.g. no plans to support Tutor) and creates an entry point to solicit contributions (e.g. help-wanted flag). |