Configuring quality standards
A quality standard decides how CaseMagic scores tickets. You set it once for the whole tenant, and can then change it for a single project, or for one ticket type within a project, such as bugs. A Tenant Admin can change every level; a project administrator can change their own project and its ticket types.
Opening the standards
- In CaseMagic, choose Quality standards from the menu.
- Choose the Level: Tenant default, or a project.
- For a project, optionally choose a Ticket type to change the standard for that type only.
If you can see a standard but not change it, the page says so.
Starting from a template
Open Start from a template and choose one. The template is copied into your standard, so you can change it freely; later product updates never change your copy.
| Template | What it checks |
|---|---|
| PD engineering | The Panoramic Data engineering readiness bar: a clear summary, a described problem, numbered steps to reproduce for bugs, testable acceptance criteria classified MUST, SHOULD or MAY, a business case, release notes and a component. |
| Generic software | A clear summary, a description and a component for every ticket. Bugs also need steps to reproduce, the expected and actual behaviour, and the environment. Stories and features need the user need, acceptance criteria and what is out of scope. |
| Service desk | A clear summary, the impact on the customer, the environment affected, evidence such as an error message or screenshot, and the Contact and Urgency fields. |
| Blank | No checks: build your own. |
Note: if a template checks a field your project does not have, such as Contact, that check switches itself off and says so on each ticket, rather than counting against every ticket.
Changing the standard
Each part of the standard (a spoke on the radar) is listed with where it comes from: Inherited from the level above, Overridden here, or Added here.
- Drag the Weight slider to make a part count for more or less.
- Clear Counts to switch a part off at this level.
- Reset to inherited takes away this level's changes to an inherited part.
- Remove takes the part away at this level.
- Open Add or replace a dimension to build a part from checks: a field must be filled in, a text must have at least a number of words, it must match a pattern, its value must be one of a list, or it must have a section with a given heading. Fields are chosen from those your project really has.
- Open Rating thresholds to set the lowest score for each rating, such as EXCELLENT from 80.
Preview, then save
Your changes are listed under Pending changes. Choose Preview on open tickets to see their effect before saving: a radar and a score distribution for the open tickets before and after the change. Nothing is saved by a preview. Add a note saying why, then choose Save; open tickets are rescored within a minute or so.
Version history
Every save is kept as a version, listed with who saved it, when, why, and what changed in plain words. Choose Revert to this to go back to an earlier version; the old version is saved again as the newest, so nothing is lost.
Quality gates
At project level, Quality gates lists the workflow transitions, such as Open to Done. Enter a minimum score and choose Set gate to refuse that transition for tickets scoring below it. The refusal shows the ticket's score, the bar and what to fix. A Tenant Admin or an administrator of the project can override a gate by giving a reason, which is recorded as a comment on the ticket.