Atlassian continues to deliver meaningful improvements to the Jira Cloud experience. The recently introduced Request Access When You Can't View a Work Item feature represents a welcome addition - particularly for organizations operating with strict permission models and robust security controls.
This feature addresses a long-standing usability gap. Previously, users encountering a link to a work item they couldn't access would face a dead end, often resorting to Slack messages, emails, or guesswork to resolve the issue. Now, users can request access directly from the point where the problem occurs a far more streamlined experience.
This is a strong step in the right direction, and Atlassian deserves recognition for addressing this need.
What the Feature Does Well
For End Users
When a user opens a work item they lack permission to view, Jira now provides a clear and actionable path forward:
- Open the work item you don't have access to
- Select Request access on the "You don't have access to this work item" screen
- Receive confirmation that the request has been sent to project administrators
The workflow is simple, intuitive, and removes friction from daily collaboration.
For Project Administrators
Administrators can efficiently review and act on access requests through a centralized interface:
- Navigate to Project settings
- Select People (for company-managed projects) or Access (for team-managed projects)
- Open Access requests
- Review the request and assign the appropriate project role
This approach centralizes access management and eliminates the need for scattered approvals across multiple communication channels.
⚠️ The Current Limitation: Missing Work Item Context
While the feature delivers substantial value, there is one critical limitation that significantly impacts its effectiveness, particularly in large-scale or highly regulated environments.
What's Missing Today
When an administrator receives an access request, the notification indicates only that access to the project has been requested. It does not specify which work item (issue key) the user originally attempted to access.
This creates ambiguity for administrators:
- Did the user need access to a single work item, or do they require full project access?
- Is this a one-off exception or an indicator of broader access requirements?
- What level of permission is truly appropriate for this request?
The resulting challenges include:
- Over-provisioning of access - granting broader permissions than necessary
- Increased administrative overhead - back-and-forth communication with requesters
- Delayed approvals - extended resolution times for straightforward requests
- Weakened permission governance - reduced confidence in access control decisions
Suggested Enhancement: Include Work Item Context in Access Requests
To make this feature truly enterprise-ready, incorporating work item context into access requests would be highly valuable.
Recommended Enhancements
When a user submits an access request, Jira should capture and display:
- Work item key (e.g.,
PROJ-999)
- Work item summary
- Direct link to the work item
- Request type indicator - distinguishing between requests for a specific work item versus general project access
This information should be visible in two locations:
- The Access requests page within Project settings
- Email notifications sent to project administrators
Why This Enhancement Matters
Adding work item visibility to access requests would deliver meaningful benefits:
- Enables the principle of least privilege - administrators can grant precisely the access required
- Accelerates decision-making - clear context reduces the need for additional investigation
- Reduces administrative burden - fewer follow-up conversations with requesters
- Strengthens security posture - improved audit readiness and access control documentation
- Aligns with enterprise requirements - supports how Jira is used in large-scale, regulated environments
A Constructive Recommendation to Atlassian
The Request Access feature is already a meaningful usability improvement. With the addition of work item context-specifically identifying which issue triggered the request-it could evolve into a best-in-class access governance capability within Jira Cloud.
I encourage Atlassian to consider this enhancement, as it would benefit both administrators and end users across organizations of all sizes.
Thank you to the Atlassian team for continuously listening to community feedback and improving Jira Cloud. The commitment to iterative improvement is evident, and I look forward to seeing how this feature evolves.
Updated Post:
Please watch, vote & comment the feature request
JRACLOUD-97042
