Concourse Feedback
Your feedback drives the Concourse roadmap! Review and vote for existing ideas or submit new ideas.
For immediate technical support, please follow this guidance to open a Service Now ticket.
Your feedback drives the Concourse roadmap! Review and vote for existing ideas or submit new ideas.
For immediate technical support, please follow this guidance to open a Service Now ticket.
As an 'Engagement Manager' or 'Other Manager' (both assigned roles in Concourse) I should have access to a 'Self Service Portal' in Jira Cloud for my 'Space' so that I can carry out various administrative and maintenance tasks.
For example, from the 'Self Service Portal' in Jira Cloud the Engagement Manager' or 'Other Manager' should be able to Administrate Permissions, Manage Issue Layouts, Edit Workflows, View Development Tools, Issue Type Scheme, Edit Work Item Layouts, Create New Work Item Types, Add/Edit/Modify Work Item Fields, etc. (this list is illustrative and not exhaustive).
For acknowledgement, there is likely a case to be made that a user should be required to demonstrate a certain level of proficiency on the platform before being granted certain abilities or rights.
Having access to a 'Self Service Portal' to carry out various administrative and maintenance tasks would enable an 'Engagement Manager' or 'Other Manager' to action tasks more efficiently that currently become blockers by having to stop, write up a service request ticket, wait for the service request ticket to be triaged, wait for the service request ticket to be actioned. Separately, it would free up capacity for the Jira Administration team to focus on higher value configuration or consultative tasks.
| Workspace Territory | United States |
| Platform & Practice | Not Practice Specific |
| Technology | Other |
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
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
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
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.