Jira – What is Automatic Linking? Relationships between Jira issues
|What is it?
||Automatic linking allows easy linking of JIRA issues with Confluence pages. The activity only needs to be completed on one of the applications for the link to be created for both.
||Automatic linking allows a user to specific additional detail in the Confluence page that is pertinent and relevant to the issue type it is linked to.
For example, Wireframe diagrams; Solution design diagrams; Query pages
||JIRA issues can also be automatically created from highlighted text within Confluence. Once the issue is created in the relevant project, the issue links are updated in the newly created issue and in the associated confluence page.
What is the relationship between Issues, Fields & Schemes?
||Issues types enables you to keep track of different items — bugs, tasks, etc. Each issue type can act differently, e.g. to follow a different process flow or track different pieces of information.
|Issue type schemes
||Is applied to projects and defines (or restricts) which issue types are available to those projects.
||Defines the steps (i.e. statuses) and transitions to other steps that an issue moves through during its lifecycle. Screens can also be mapped to different transitions of a workflow.
||Associates Workflows with issue types, which in turn is applied to projects. This allows you to specify different workflows for each type of issue in a given project.
||A set of definitions for all fields, comprising: Field description; Visible vs hidden; Mandatory vs optional; type of renderer for a text field.
|Field Configuration scheme
||Associates field configurations with issue types, which in turn is applied to projects. This allows you to specify different behaviours for a field, for each type of issue in a given project.
||Defines which fields are present on a screen, and their order.
||associates different screens with different issue operations (e.g. ‘Create Issue’, ‘Edit Issue’, ‘View Issue’).
|Issue type screen schemes
||Associates screen schemes with issue types, which in turn is applied to projects. This allows you to specify different screens for a particular operation (e.g. ‘Create Issue’), for each type of issue in a given project
If the field configuration scheme, issue type screen scheme, and workflow scheme associated with a given project contain associations with other issue types that are not specified in the project’s issue type scheme, then those other issue types will be ignored by the project since the project’s Issue Type Scheme restricts what issue types the project can use.