The diagram below describes how the branching strategy will relate to work flow and workflow states.
The release candidate branch is a permanent branch.
When a content project is identified, a ticket (project) is created in JIRA, and a corresponding branch is created, from the release candidate branch, in the terminology server (TS).
The Project ID in JIRA is associated with the the TS branch.
All SNOMED CT components that are created and edited as part of the project are associated with the project branch, and therefore traceable back to the JIRA ticket.
Workflow state is managed in JIRA. Applications that need to know the workflow state of a project at any time, use the JIRA API to look it up in JIRA.
Content is created and edited on task branches, which are derived from project branches.