Schemes
Schemes finds the work types, priorities, resolutions and link types that no work item has, with the flows that still name them, and shows where each group and project role is granted. It reads Jira and changes nothing.
On this page
Before you start
Schemes is for Jira admins. A Jira admin turns on its background checks in Schemes settings. Until then TuneCraft reads nothing. The first reading starts within the hour. A space's roles are read in turns, a quarter of the spaces in each reading. Checks run weekly where the site's points allow, and less often on large sites.
Work types and priorities
The Work types and priorities page lists your work types, priorities, resolutions and link types. For each it shows the work items that have it, as Jira counts them, and the flows of the last scan that name it. The ones that no work item has come first.
- One that no work item has, and no flow names, may go.
- A work type, priority or resolution that work items have is never proposed, whatever its name. The work items would need another one first.
- Jira counts the work items TuneCraft can browse. An object on no work item whose flows were not checked says so: scan your flows first.
- Objects of one name, compared without case, spaces or punctuation, are copies. To merge two, move the work items in Jira, then delete the copy.
Grants and groups
Grants and groups shows, in your permission schemes, where each group and each project role is granted, and where it fills the roles of a space. It is configuration only: TuneCraft never reads who is in a group. It counts a role's users without keeping them.
It also points out the roles worth a look: a role that a permission scheme grants but that no space using that scheme fills, or that no space uses at all. Its grants count toward Jira's cap of 50 a permission without giving anyone access.
Filters, dashboards and notification schemes shared with a group are not read yet.
What Schemes does not do
It changes nothing in Jira. Delete work types, priorities and roles in Jira after checking the flows. Security levels are counted in the Limits tool, see Jira limits. A space whose roles Jira refuses keeps what was last read and is read again the next time.
What it keeps
For each work type, priority, resolution and link type: its id, its work items, and a code made from its name with your site's key (for copies), never the name. For each permission scheme: its grants to groups and roles, by their ids. For each space: its permission scheme, and the groups and roles filling its roles. Each count of work items is kept for a week. If you turn the checks off, what they read is removed within a day.
Questions about the app? Write to info@plugincraft.ca.