Card #1896 · Atlassian Marketplace
Inefficient handling of group access requests in JSM
Managing bulk access requests for teams is cumbersome, forcing a choice between cluttering the queue with individual tickets or using a single ticket with messy approvals. Current workarounds involving linked issues or custom automation are either confusing for approvers or difficult to build and report on.
Pain score
0.50/ 1.00 · weighted product of four components
Reach0.50distinct authors (log-normalized)
Recency0.64freshness decay, half-life months
Engagement0.39upvotes + comments, normalized
Monetization0.50willingness-to-pay cues in evidence
§ Evidence — 3 verified quotes
I either create one ticket per person which absolutely clutters up the queue and makes the dashboard look insane, or i make one big ticket with a list of names in the description, but JSM doesnt really structure that well so approvals get messy.
Is there a better way to handle group access requests without splitting everything into a million tickets?
We made a custom request type ""group access request"" with a multi-pick user field, automation splits it into individual sub-tickets after approval. Works but the build was a slog and reporting is messy.
Comments are a Pro feature — join the conversation, share what you've shipped, hear what others are building.
Upgrade to Pro