User manual
TuneCraft: Automation & Site Cleanup is a Jira Cloud app that finds the automation steps and the Jira configuration a site no longer needs, says what depends on each one, and helps you remove it. This manual covers the whole app. It is for Jira admins, for the people who own automation flows, and for project admins who look after their own project.
Terms used in this manual
| Term | Meaning |
|---|---|
| Tool | One part of the app that answers one question about your site, with its own pages, Welcome and Help. Automation, Limits, Fields, Spaces, Schemes, Filters and Labels are tools. |
| Flow | One Jira automation rule. |
| Step | What Atlassian bills for automation: every trigger, condition, action, branch and loop that runs. |
| Scan | Choosing the export of your flows (and, if you wish, the automation audit log) so that your browser reads it and TuneCraft keeps a summary. |
| Finding | A reason a flow spends more steps than it needs, or is broken, with its fix. |
| Background checks | Readings of Jira's configuration that TuneCraft makes by itself, in small parts, once a Jira admin turns them on for a tool. |
| Measured | A number read from Jira or from a file you scanned. |
| Estimated | A number TuneCraft worked out from your flows and their runs. |
Every number in the app says whether it is measured or estimated, and so does this manual.
Contents
- Getting started: installing the app, the three places it appears in Jira, and the setup guide.
- Access: who can open what, and how Jira admins give access to groups and project admins.
- Automation: scanning your flows, the findings, the savings and how they are estimated.
- Optimize and fix: the corrected flow, the import file, dependencies, copies and telling owners.
- Run health, governance and usage: failing flows, broken flows, credentials, usage and alerts.
- Fields: custom fields that may go, and fields that are copies.
- Filters and dashboards: broken, unused and orphaned filters and dashboards, and changing their owner or deleting them.
- Labels: finding copies, and renaming, merging and removing labels.
- Spaces: idle and empty spaces, stale versions, components no work item has and unused categories.
- Schemes: work types, priorities, resolutions and link types that nothing uses, and where each group is granted.
- Jira limits: how close each count is to the cap Jira sets, with forecasts and alerts.
- Administration: settings, maintenance, database size, the support bundle and App cost.
- Privacy and data: what runs where, what is stored and what never is.
- Limits and troubleshooting: the numbers that apply, common messages and what to do.
- Licence and trial: what works with a licence, during a trial and without one.
Who it is for
- Jira admins use every tool and the settings. They run scans, turn on background checks and make changes in Jira.
- People with the Manage level (a group a Jira admin chose) scan exports, download fixes and tell owners, but cannot change settings.
- People with the View level read the reports and findings.
- Project admins see and fix the flows that run only in their own project, if a Jira admin allows it.
Questions about the app? Write to info@plugincraft.ca.