...
§4: The workflow is generally (a) TO DO → (b) selected for development → (c) in progress → (d) in review → (e) done. The state "in review" is a bit badly named, but it is optional for teams to use and it describes the situation that a development team considers the item as done, but the PO (product owner or similar representative/delegate of the team) has not formally accepted it yet. As of Jan-2020 this state only used by team T4 (Avinoam). JIRA also has a name for each state transition under the "workflow context menu) as follows: Assign near-term schedule (TO DO→selected for development), start work (selected for development→in progress), done, but waiting for approval (in progress → in review), approved (in review → done), done and no further approval (in progress → done). Again, note that the "grayed out" state transitions as of Jan-2020 are only used by team T4 (Avinoam). For all other teams a JIRA items go through creation and three transitions passing through four states.
§5.1: JIRA has a concept of releases (aka versions). We use this naming convention: Bronze-R3, Bronze-R4, Cherry-R5, Cherry-R6. R3 and R4 are the first and second half of Bronze. A release ZZZ_future is used to indicate items that are not yet planned to be worked on any time soon. A release ZZZ_never is used to indicate items we never plan to work on (Jira's Resolution field (with the state "won't do") is not used for anything). This way at least (new) epics that do not have any release version as "fix version", must be analyzed still on when they are to be worked on.
...