Concourse & Jira Cloud Portal
There are few areas where delivery teams will need to do some project modifications in Jira, however, they cannot manage them without PMO / Jira Cloud Admin team. It will cause huge overload for Admin team during mass adoption as each project team will need to do some customization:
Adding new fields
Adding / changing values to existing dropdowns
Hiding fields for all project users
Change status workflows
Create / update / remove automations
Thanks for the feedback — this is a common need as Jira adoption scales. At this time, changes such as adding fields, modifying dropdown values, updating workflows, hiding fields, or managing automations must go through the PMO Hub to ensure enterprise governance and reporting consistency. This centralized approach helps prevent configuration sprawl and cross-project impacts. That said, this feedback is driving the research and development of a self-service portal within Jira, which would give extra permissions for some of these things like adding fields and managing dropdown values within defined guardrails.