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.
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
| Workspace Territory | N/A |
| Technology | Salesforce |
Following up with an update. Delegating routine project changes — especially dropdown values, fields, workflows, and automations — without an admin ticket is part of the Jira Cloud Self-Service Portal work (ADO epic #1401215 / Aha CONC-E-1378).
The first capability we are considering for the next PI that maps most directly is Manage Dropdown Options for Your Project (Aha CONC-6187 / ADO #1432016). It is tagged for PI consideration and is not yet PI committed.
Asks such as adding new fields, changing workflows, and creating/updating automations are understood and remain out of the current bundle. Portal launch depends on a set of features shipping together, internal approvals, and user testing we anticipate with the PwC Atlassian Champions Community. We will continue to update as these Features get developed further and shipped. Thank you.
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.