Who it is for
- Jira admins who inherited a site with more fields, workflows, and schemes than anyone can explain.
- Platform owners whose Jira grew space by space, with each team adding its own rules and nobody owning the whole.
- Teams planning a migration, a site consolidation, or a Rovo rollout who want to know what they are carrying into it.
What you get
- Accounts and groups: users who still hold Jira access but have not been seen in months, groups that grant access nobody can explain, and groups with no owner.
- Permission schemes: who can browse, edit, delete, and administer in each space, where broad groups hold more than the work needs, and schemes no space uses.
- Custom fields: duplicates with near-identical names, fields with a global context, fields nobody fills in, and, on Cloud, spaces close to the 700-field limit per space.
- Workflows and screens: copies made per space, statuses that mean the same thing under different names, and screens that show fields no one uses.
- Governance: who can create spaces, fields, and workflows today, and whether any change to configuration goes through review.
- A written scorecard in that order, with a 30-minute walkthrough and a short list of what to fix first.
How it works
- Intro call (30 minutes). We confirm your plan, the spaces that matter most, and the access we need. You leave the call knowing exactly what to send.
- Review (about 1 week). We work through your site in our cleanup order: accounts and groups, permission schemes, custom fields, workflows and screens, then governance. We look and record. We do not change configuration.
- Walkthrough (30 minutes). We walk your team through the scorecard, explain each finding, and name the fixes that matter most. The scorecard is yours to keep.
What we need from you
- A Jira administrator account for the review period, or a screen-share with your Jira admin if your policy rules that out.
- A user export with group memberships and last activity dates. On Cloud, the export from Atlassian Administration includes both.
- A short list of the spaces and teams that matter most, so the scorecard weights them.
- Your Jira plan (Free, Standard, Premium, Enterprise, or Data Center), since some checks use tools only certain plans have.
Related reading
- Why capacity planning in Jira starts with cleanup: why plans built on an unsettled site do not hold.
- Jira cleanup and standardization: the work that follows, if you want help with the fixes.
Questions
Is the health check really free?
Yes. There is no charge and no commitment. You keep the scorecard. If you want help with the fixes, it becomes the plan for the cleanup. If not, your team can work from it on its own.
Will you change anything in our Jira?
No. We review and report. Configuration stays exactly as it is until you decide what to change and who should change it.
Why do you start with accounts and groups?
Permission schemes grant access through groups and roles. If group membership is wrong, a clean scheme still gives the wrong people access. So we settle who has access first, then what they can do, then the fields and workflows they work in.
Does it cover Jira Data Center?
Yes. The review order is the same. Some checks use different tools: on Cloud Premium and Enterprise, Jira's site optimizer shows when each custom field was last used, and on Data Center, the custom field optimizer flags fields with global contexts, and usage data shows fields that have not been used in a long time.