r/jira • u/terselogic • 14h ago
Advertising Built a read-only Forge app to audit Jira permission schemes before enabling Rovo / MCP (zero external egress)
With more teams looking at Rovo and MCP integrations, one recurring governance risk we kept seeing is legacy Jira permission schemes: anyone (anonymous) grants, unrestricted applicationRole access on critical permissions (ADMINISTER_PROJECTS, BROWSE_PROJECTS, EDIT_ISSUES, DELETE_ISSUES, etc.), or broad default groups like jira-software-users holding admin/delete rights.
Since native Audit Logs don't show structured before/after config diffs for permission schemes and workflows, I built a small Forge app (Permission Hygiene & Config Diff Auditor) focused strictly on read-only auditing:
- Permission Hygiene Scan: Flags
anyoneaccess, all-logged-in-user grants, broad default groups, and unused permission schemes with HIGH/MEDIUM/LOW severity. - Config Diff Auditor: Takes deterministic JSON snapshots of permission schemes, project mappings, and workflows, and surfaces exact
ADDED/MODIFIED/REMOVEDdiffs via a daily scheduled trigger or on-demand scan. - Runs on Atlassian (Forge): Uses Node.js 24 + Forge SQL (MySQL) inside the Atlassian Cloud boundary with zero external server egress and only read/config scopes (
read:jira-work,read:jira-user,manage:jira-configuration).
It is currently in Atlassian Marketplace review (App ID 3567210724). Architecture notes and screenshots are here if anyone wants to review or give feedback on what rules/checks are most useful before turning on Rovo:
https://terselogic.com/atlassian/permission-hygiene-auditor/
Would love to hear from Jira admins: what permission or workflow drift checks do you usually run manually before an audit or AI rollout?