Loading
Years of Jira administration can leave behind hundreds of workflows, schemes, fields and screens — many duplicated, unused or difficult to assess safely.
ConfiSense gives Jira Cloud administrators an evidence-based view of that configuration: what exists, where it is used, what depends on it and what may need attention.
For identical workflows, ConfiSense goes further — enabling consolidation with recorded restore points and rollback.
ConfiSense
Large Jira environments accumulate configuration over time.
Workflows are copied. Schemes multiply. Fields and screens remain long after their original purpose has disappeared. Administrators are often left managing objects they did not create, with limited certainty about what can safely be changed.
ConfiSense brings that configuration into view.
It analyses the site, identifies duplication and disuse, and shows the evidence behind each finding so administrators can make decisions with greater confidence.
ConfiSense
See where attention is needed.
ConfiSense provides an overall optimisation score for the site, supported by scores across individual configuration domains.
A Quick Action View highlights what needs attention, what requires review and what has changed recently.
Instance Health reports can also be published to Confluence.
Scans can be run on demand or scheduled from App Settings.
ConfiSense
Analyse the areas that create complexity.
ConfiSense analyses multiple Jira configuration domains independently.
Analysis is read-only. No configuration is changed until an administrator confirms an action.
ConfiSense
Understand an object before you touch it.
Search for a configuration object and see its role within the wider Jira environment.
For each object, ConfiSense can show:
ConfiSense
Consolidate identical workflows with a way back.
Where ConfiSense identifies identical workflows, administrators can select the workflow to retain and review exactly which workflow schemes will be affected before confirming the change.
For every affected scheme, ConfiSense creates a restore point, applies the new workflow mapping and records the outcome.
Work items are not migrated, moved or edited. Only the workflow mapping on the scheme changes.
Each scheme is processed independently so the result of one does not obscure what happened to another.
Review shows where near-identical workflows differ, whether in transitions, rules or app settings, so you can decide what needs attention before anything is changed. Each group can be marked as reviewed.
ConfiSense
Every consolidation is reversible.
Each workflow consolidation is recorded in History and can be rolled back.
Before rollback, ConfiSense shows the schemes that will be affected. The previous mapping is then restored using the same restore-point mechanism and the result is recorded.
ConfiSense
Reassign filters and dashboards when ownership changes.
Find filters and dashboards by owner, identify entities belonging to inactive users, and transfer ownership to another active user.
Every transfer is recorded for later review.
ConfiSense
ConfiSense bases its findings on information returned by Jira during analysis.
Where the available data is not sufficient to reach a reliable conclusion, the app reports that explicitly rather than filling the gap with an assumption.
Counts and statuses are therefore presented with the evidence available at the time of analysis, including timestamps where relevant.
ConfiSense
ConfiSense is designed around controlled change.
ConfiSense
ConfiSense is built on Atlassian Forge.
Analysis results and run records are stored in Forge storage on the Jira site. The app makes no calls outside Atlassian infrastructure and operates without external servers or third-party storage.
ConfiSense is intended for Jira Cloud administrators responsible for environments where configuration has accumulated over years and the impact of change needs to be understood before action is taken.
The current V1 is designed with environments in the approximately 2,000–10,000 user range in mind.
ConfiSense V1 currently supports workflow consolidation.
Other configuration domains provide analysis and review capability but are not consolidated by the app.
Team-managed projects are excluded from scheme analysis because they do not use site schemes.
Automation rules are not read or transferred.
Platform: Jira Cloud
Access: Jira administrator permission is required for analysis and consolidation.
Understand what is there before deciding what should change.
Use ConfiSense to analyse Jira configuration, investigate dependencies and impact, and consolidate identical workflows with a recorded path back.
