...
To apply such mapping, navigate to “…” menu in any issue view → SM - Administration Scrum Maister settings in the Project menu on the left → Project Settings → (scroll to bottom) “Scrum Maister” → “Map custom issue types” tab.
...
In some cases, the standard Jira Story points field is not used, and companies utilize other fields for a similar purpose. It is possible to point SM to a field that is responsible for Story points in your project.
To do this, navigate to “…” menu in any issue view → SM - Administration Scrum Maister settings in the Project menu on the left → Project Settings → (scroll to bottom) “Scrum Maister” → “Issue Analytics” tab. There, scroll to the bottom and enter the internal Jira field ID and save the changes.
...
SM allows enabling a check that verifies that the Acceptance criteria section is present in Story description. To activate it, go to “…” menu in any issue view → SM - Administration → Issue analytics - navigate to Scrum Maister settings in the Project menu on the left → Project Settings → (scroll to bottom) “Scrum Maister” → Acceptance criteria is specified in Story Description
...
Stories are linked to Features as “relates to”
Tasks are linked to Stories as “relates to”
To enable them, proceed to “…” menu in any issue view → SM - Administration navigate to Scrum Maister settings in the Project menu on the left → Project Settings → (scroll to bottom) “Scrum Maister” → Issue analytics
...
In the future, the custom mapping will be implemented to allow any issue and link types.
...
In this case, the lack of ownership check does not add value and can be disabled. To do so, navigate to “…” menu in any issue view → SM - Administration Scrum Maister settings in the Project menu on the left → Project Settings → (scroll to bottom) “Scrum Maister” → Sprint and Kanban Analytics and uncheck “Detect lack of ownership for issues”.