TuneCraft: Automation & Site Cleanup for Jira Cloud
Everything TuneCraft does
The full list, grouped by what you want to get done. Everything here is built in the app today. Planned features are not listed. The user manual explains how each one works.
Find wasted automation steps
- Upload Jira's export Export your automation flows from Jira settings and choose the files in TuneCraft. Your browser reads them. A second file, Jira's automation audit log, is optional and gives the real runs and steps of each flow.
- Secrets stay in the browser Web request addresses, headers, email addresses, JQL, smart values and other free text are replaced by placeholders in your browser before anything is sent. TuneCraft keeps only the flow's structure.
- Findings, each with its cost and its fix Broad triggers, conditions placed late, flows that start themselves or each other, frequent scheduled searches, branches over many work items, lookups and web requests inside branches, empty if/else blocks, and custom fields that flows keep up to date but no screen shows. Each finding says why it costs steps, how to fix it and how many steps a month the fix may save.
- Copies and shared triggers Flows that do exactly the same, and several flows on one event, each paying its own trigger step. TuneCraft shows what turning off the extra ones saves.
- Broken flows Flows that name something Jira no longer has, or has differently: a field in the trash, a deleted or renamed status, an archived project, a deactivated owner. This check is measured against Jira, not estimated.
- Governance and service limits Credentials in a web request header, email to addresses outside your domains, and flows near Jira's service limits, such as 65 components in a flow or a scheduled search that finds close to 999 work items.
Fix the flows and follow the savings
- Overview and scorecard Flows scanned, flows with findings, findings by severity, and steps a month now and after the fixes, set against what your Jira plan includes.
- Optimize Pick a flow and see the changes step by step, the flow as it is and corrected side by side, and download the corrected flow, ready to import into Jira. Your browser puts the real values back. Jira offers no way for an app to write a rule, so you import the file.
- Saved, Can still save and History Fixes confirmed by a later upload, with the steps saved a month. The open findings ranked by monthly saving. One point per upload, as a chart and a table.
- Dependencies and impact Which flows can start others, the loops among them, and what a change to a flow could affect, with the owners of those flows.
- Tell the owners One Jira work item for each owner a change affects, created as you. Jira sends its own emails and the owners answer on the work item.
- Merge copies A flow's copies with the one that stays, how to run it in all their projects, and how to turn the others off.
- Assumptions How Jira counts steps, the estimates TuneCraft uses with your site's own values, and the runs or steps you measured yourself. Every number says whether it is measured or estimated.
Usage, forecast and alerts
- Usage Runs and steps a month for each flow, and the site's steps each day, kept for 400 days from every audit log you scan.
- Forecast This month's steps at their current pace against your allowance. The page says whether the figure is measured or estimated.
- Alerts A Jira work item when the forecast reaches 80% and 100% of the allowance, once for each, each month. A Jira admin picks the project and the people mentioned.
Jira's limits
- Distance to each limit How close each space and scheme is to the limits Jira enforces, such as fields and work types per space, options per field and statuses per workflow. Jira refuses new configuration once a limit is reached.
- History and forecast Counts kept when they change, and the day a limit would be reached at the current pace (estimated).
- Alerts A Jira work item when a count passes 80% of its cap, would reach it within 30 days, or reaches it.
- Work items near their caps Jira's limits on attachments, links, comments, worklogs and watchers for a single work item, with Done work items left out.
- Flows that use up limits Flows that create versions, comments, links, worklogs, attachments or options on a recurring trigger, set beside each space's growth.
- TuneCraft's own use of Jira's API The points TuneCraft spends each day and the times Jira refused a call, on the App cost page.
Fields
- Unused and stale custom fields Per field: when it was last used, its screens, contexts, projects, values, and the flows and filters that use it. Locked fields and fields added by apps are never proposed.
- Copies of a field Fields with the same normalized name and type, with their use and a suggestion of which to keep. A daily check finds new copies.
Labels
- Every label, its work items and its flows Labels that differ only by case or one letter are shown as copies.
- Rename, merge and remove Across work items, with the flows the edits would wake shown first. A record file lets you undo a change.
Spaces, versions and components
- Idle and empty spaces Last update, work items, the state of the lead, and the flows still running there with the steps a month they cost.
- Project categories The categories no project uses.
- Versions and components Reports on stale and overdue versions, and on components no work item has.
Filters and dashboards
- Filters Filters whose JQL Jira refuses, whose owner is deactivated, that nobody used for the months you set, and copies. Each shows the flows that use it.
- Dashboards Dashboards with a deactivated owner, or no favourites. A Jira admin can change the owner or delete a dashboard they own.
Work types, priorities and schemes
- Work types, priorities, resolutions and link types Their use by work items and flows, and copies by name. A type or priority that something uses is never proposed.
- Groups and roles Where each group and role is granted, and which roles no space fills. TuneCraft shows the grants, never who is in a group.
Before TuneCraft changes anything in Jira
- Check before you delete For a field, option, status, project, version, component, work type, priority, resolution, link type, label, filter, group or person, the flows of the last scan that use it. If TuneCraft cannot know, it says so and never says that no flow uses it.
- Preview and live re-check Every change is previewed, and its evidence is read again from Jira just before it runs.
- Confirmation, record and undo Nothing changes without a confirmation. Every change is recorded with who made it, and has an undo where Jira allows one.
Access, languages and administration
- Who can use it Jira admins always can, and only they change the settings. They can let groups open TuneCraft at View, to read, or at Manage, to also scan, download fixes and send notices. Project admins see the flows that run only in their own project.
- In Jira's own look TuneCraft follows your site's light or dark theme and your language: English, French, German, Spanish, Italian, Japanese, Simplified Chinese and Hindi.
- Maintenance and support Daily clean-up tasks, the size of the database against its limit, and a support bundle that holds versions, the licence state and table sizes, never your flows or people.
- Personal data The account ids TuneCraft stores are reported to Atlassian once per reporting cycle, and those of closed accounts are erased.
TuneCraft is not on the Atlassian Marketplace yet. Questions in the meantime? Write to info@plugincraft.ca.
Email us