Hi everyone,
We are currently facing a scaling and maintenance issue with how our user groups are structured in Jira, and we’d love to hear how other admins have solved this.
The Context:We have a very large number of groups named after specific managers (e.g., team-john-doe or similar). Because these represent dynamic business teams rather than rigid organizational departments, we don't have fixed department names we can easily fall back on.
The Problem:Whenever a manager changes roles, leaves, or their last name changes, we have to rename or recreate the group. Since JQL filters reference the group name rather than a static Group ID, changing a group name breaks existing filters, boards, and dashboards across the instance. Worse yet, as admins, we don't have full visibility into how many private or shared user filters rely on a specific manager-based group before we touch it.
Our Questions:
- Naming Convention: What naming convention would you recommend for dynamic business teams that don't belong to a rigid department structure, so we can completely decouple group names from individual managers?
- Migration Process: What is the safest, step-by-step approach to clean this up and migrate users to a new group structure without causing massive disruption to users' existing filters and boards?
- Architecture / Feature Question: On a broader note – why do Jira filters still bind to the group name instead of an immutable Group ID (similar to how Custom Fields or Users via
accountId work)? Shouldn't Atlassian consider changing this behavior to make group management less fragile?
Any advice, scripts, or lessons learned from similar cleanups would be greatly appreciated!
Thanks in advance!
*As an aside, unfortunately, we do not use ScriptRunner or other plugins in our instance.