+1 for this request. The inability to edit transition rules badly hampers the usefulness of this feature. Ideally as much as possible should be decentralised to the teams so that the workflow can be a living thing that accurately reflects how teams work, and prevents them from getting into trouble as much as possible. I was hoping that perhaps the Jira Automation would allow a way to do this instead, but sadly there are no options there for adding transition rules.

I would argue that the inaccessibility of workflow management is often what prevents teams from editing their workflows at all. Teams that often don't have much experience with Jira may even just assume at face value that the workflow they have is simply "how Jira works". In reality, workflows should be alive and represent how a team works best independently of the tool.

My hunch is that the lack of this project-level permission (and lack of evangelization of workflow experimentation as part of the UX) is the largest reason why Jira has a bad reputation in agile environments.

I could not agree more. If I need to make a change I have to wait for our admins in India to come on line the next day, log in during my night, and tell them exactly which buttons to push.

+1. @scott.nelson4 (Super Steve) said it best.

The point is to become more Agile, not more dependent on centralized administration.

This is such a bottleneck and huge impediment to leveraging the full capabilities of Jira. 

If you are looking for project admin to update workflow condition/validator/post-function, the Workflow Rules plugin may be for you.

It works with extended project administration permission and allows project admin to define natural language like rules for project-specific workflow transition.

+1.  Too much work for the full admins.  Having workflows, screens, and fields that are local and not global would reduce the amount of time Jira admins spend getting projects started.  If a project admin breaks their workflow, it's not the Jira admin's problem.

With the growing demand for Agile transformations (especially in California and Utah), it will become more commonplace for Project Administrators (typically Agile Coaches and Scrum Masters) to need to revise Workflows.  Transforming organizations (be it teams or entire enterprises), should not require a bunch of red tape.  The point is to become more Agile, not more dependent on centralized administration.

My instance of Jira has 600 projects, 10,000 users.  The idea of would be admins thinking they know what they are doing blowing up work, becuase they don't know what they are doing is mind bending and will create more work in the long run, first with trying to figure out what they blew up and the next in fixing it.  Each project has at least 3 admins, who all think they are wonderkids, they are not.  Having to edit 600 projects to either grant or not grant these admin permissions is crazy talk.  My full admins don't have time to train people, but that is what will eventually happen; everyone will want the full admins to review the work before it is implmented so now what are your admins doing? more busy work. 

+1 – I always feel like I am dragging my Jira admin into work they really shouldn't be doing. Just to get a comment screen added to a workflow transition, for example.