Dependency Integrity for Confluence
In researchUnderstanding Confluence app dependencies before a change becomes a problem.
A proposed tool to help teams understand which Confluence content and configuration may depend on a Marketplace app before it is disabled, uninstalled, replaced, or migrated.
Concept, not a product release
Dependency Integrity has not been built or submitted to Atlassian. The problem, possible use cases, and technical feasibility are being validated before development scope is set.
The research question
What depends on an app before that app changes?
Before disabling, replacing, uninstalling, or migrating a Marketplace app, teams may need to understand which Confluence content and configuration depend on it.
The research asks whether a focused assessment before a change could make those dependencies easier to find and document. It also asks whether Confluence APIs and accessible data can support a useful product.
Potential dependency areas
The places an app may leave a footprint.
These are areas under consideration, not functionality that exists today.
What we're trying to learn
Questions for people who have dealt with this problem.
Which dependencies are hardest to identify today?
When are dependencies usually discovered?
What information is needed before removing or replacing an app?
Would a pre-removal impact report be useful?
Which Confluence APIs or data-access limitations affect feasibility?
No dependency scan, report, or remediation workflow exists today. Current work is limited to validating the problem and researching technical feasibility.
Share practical experience
Have you discovered app dependencies too late?
Brian is looking for candid feedback from people who have planned Confluence migrations, app replacements, or removals.