Jira Cloud Self Service Portal for Space Admin & Maintenance

Agreed

Thank you for this feedback, and for the 197 endorsements behind it. The need for Engagement Managers and Other Managers to complete routine Jira Cloud space administration without a service ticket is well understood, and it is actively shaping the Self-Service Portal work.

Where we are this Program Increment (PI):
Work has begun this PI on the initial framework of the Self-Service Portal in Jira Cloud. That foundation covers how the portal is discovered, how a user selects an eligible project, and how role-based access is enforced so later capabilities can be added safely.

Aha: CONC-6110 — Establish Self-Service Portal Initial Setup in Jira Cloud
ADO: #1408971 (parent epic #1401215 / Aha CONC-E-1378)
This first slice does not yet include permissions administration, workflow or layout editing, or new work item types. Those remain out of scope for the framework itself.

What we are considering for the upcoming PI
We are planning a first set of portal capabilities for the upcoming PI, subject to PI planning. The items currently under consideration are:

• Manage dropdown options for your project — CONC-6187 / #1432016

• Access guides and help from one place — CONC-6188 / #1432049

• See who changed what and when — CONC-6189 / #1432065

• Self-service project plan import — #1678622

• Self-service bulk update of Jira work items from CSV — #1678623
  
  

On launch timing
The portal will not go live as a single framework drop. Launch depends on a bundle of features shipping together, internal approvals, and user testing we anticipate running with the PwC Atlassian Champions Community. Until that bundle, approval path, and Champion testing are complete, the portal should be treated as in development rather than generally available.

We will keep this idea updated as planning for the upcoming PI firms up. Input like this continues to help us sequence what project leads can do themselves versus what should stay with Jira administration. Thanks again. We'll be in contact as this develops further.

Hi Klinttin - not sure if you are familiar with Rovo - Atlassian's AI-assistant but I thought I'd share the feedback of your query since I know that some (not all) of those capabilities already exist if you have the right permissions within Jira. We also have the ability to build Agents and Automations to help out as well within Jira Studio so maybe this might come as helpful:

Much of what your feedback describes already exists or is actively shipping in Jira Cloud, though not as a single unified "Self Service Portal." Here's the breakdown:

What already exists today

1. Extended Project Admin Permissions — This is the closest match to the core ask. Jira Cloud has shipped two delegatable permissions that previously required full Jira admin access:

   • Manage Issue Layouts — allows non-admins to edit issue layouts in company-managed projects (where the underlying screen is isolated)

   • Edit Workflows — allows non-admins to modify statuses and transitions on isolated workflows in their project

   These shipped to all customers in late 2024. Jira admins grant these via Settings → Permission Schemes. https://jira.atlassian.com/browse/JRACLOUD-70190 · https://jira.atlassian.com/browse/JRACLOUD-62881

2. Space Roles & Permission Delegation — In both company-managed and team-managed projects, Jira admins can assign project roles with specific permissions (Administer Projects, Browse Projects, etc.) so that Engagement Managers or similar roles can manage users, permissions, and access within their space without a site-admin ticket. Customize Jira Service Management permissions | Jira Service Management Cloud | Atlassian Support

3. Team-managed spaces — These give project leads direct control over workflows, issue types, fields, and access without needing Jira admin involvement at all. If applicable, this model is the closest to the "self-service portal" concept.

What does NOT yet exist as self-service

Several items from the feedback's illustrative list still require Jira admin access:

• Issue Type Schemes — creating or modifying issue type schemes is admin-only

• Adding/modifying custom fields (globally) — still admin-controlled

• Creating new work item types — admin-only in company-managed projects

• Development tool integrations — admin-level configuration

• A unified "Self Service Portal" UI consolidating all of these — this does not exist as a single experience

The proficiency gating idea

The feedback's suggestion that users should "demonstrate proficiency before being granted certain abilities" doesn't have a direct equivalent in Jira Cloud. The current model relies on admins manually granting permissions rather than qualification-based access.

In summary: The pain point is real and recognized. Jira has been incrementally addressing it by delegating specific admin capabilities (workflows, issue layouts) to project-level roles, but a comprehensive self-service admin portal for space managers doesn't exist yet. The feedback would be most impactful as a request to expand the set of delegatable permissions and potentially wrap them in a discoverable project-level settings experience.

16 Sources

Thank you for this submission, Klinttin. We are actively looking at the Self Service Portal design and appreciate your input. Our Jira Cloud Product Manager will be in touch as the refinement progresses.