2 ms·

Well... for us every team gets a "Project" and the Team Lead is admin for the Project. The TL can then Create Boards, Issue Types, and Workflows. The Team is in

Well... for us every team gets a "Project" and the Team Lead is admin for the Project. The TL can then Create Boards, Issue Types, and Workflows. The Team is in control of what their Board and Workflows look like. Not some far away manager and if we do need the company Jira Admin to do something, it just needs a IT Support Ticket and that will be handled. We set up our Board and Workflow fairly minimal. Which is probably why I don't have any problems with Jira. > And "transitions are impossible by default and only possible if enabled by the admin" is a uniquely bad Jira-ism that other tools in this space don't have What do you mean by that? The default Workflow in Jira is that all Issues can transition into any status.

lmm 3y ago
> The default Workflow in Jira is that all Issues can transition into any status. The default workflow in some newer editions has a transition that allows that yes. But custom workflows don't have those transitions unless and until an admin manually adds them. If the person who set up the workflow didn't think of some edge case, you're SOL.
- VonGallifrey 3y ago
  Since the person that made the workflow is always the Team Lead we are never "SOL". It is a 2 minute thing to fix a workflow. Sounds to me like you probably never edited the Jira workflows yourself. If it takes your company more then an hour to change a workflow then that is a decision to artificially limit things. Also: Custom workflows start with with the "Any" transition on all states and when adding a new status it also has the "Any" transition. If that is different in your workflows then that is a deliberate decision.
  - lmm 3y ago
    > Sounds to me like you probably never edited the Jira workflows yourself. If it takes your company more then an hour to change a workflow then that is a decision to artificially limit things. I've never been able to edit the workflow, except at one company where I had access to the "beta" Jira but not the "real" one. This is across, like, five or six different companies - again, if it were one company I'd say it's a bad decision by that company, but the fact that it's so consistently done this way tells me it's something about the tool. > Also: Custom workflows start with with the "Any" transition on all states and when adding a new status it also has the "Any" transition. If that is different in your workflows then that is a deliberate decision. Wasn't the case as recently as 2020 (the last time I had access to create my own custom workflow, and I'm pretty sure that was a newer version of Jira than many large companies are using). Are you using the cloud version or something?
    - VonGallifrey 3y ago
      I am using the Cloud version, but I have been using Jira over the last 10~12 Years at different companies. I can't remember a time where transitions where restricted by default. I always preferred a less restricted workflow if I am working with a I can trust, but I can't remember needing to change workflows to enable transitions from a default. What I wanted to get across is that Jira makes it very easy to give control to the Team that is using a specific Board or Workflow. If your company don't trust their Teams with that then that is a failure of the company and not a failure of Jira.

lmm 3y ago

> The default Workflow in Jira is that all Issues can transition into any status. The default workflow in some newer editions has a transition that allows that yes. But custom workflows don't have those transitions unless and until an admin manually adds them. If the person who set up the workflow didn't think of some edge case, you're SOL.

VonGallifrey 3y ago
Since the person that made the workflow is always the Team Lead we are never "SOL". It is a 2 minute thing to fix a workflow. Sounds to me like you probably never edited the Jira workflows yourself. If it takes your company more then an hour to change a workflow then that is a decision to artificially limit things. Also: Custom workflows start with with the "Any" transition on all states and when adding a new status it also has the "Any" transition. If that is different in your workflows then that is a deliberate decision.
- lmm 3y ago
  > Sounds to me like you probably never edited the Jira workflows yourself. If it takes your company more then an hour to change a workflow then that is a decision to artificially limit things. I've never been able to edit the workflow, except at one company where I had access to the "beta" Jira but not the "real" one. This is across, like, five or six different companies - again, if it were one company I'd say it's a bad decision by that company, but the fact that it's so consistently done this way tells me it's something about the tool. > Also: Custom workflows start with with the "Any" transition on all states and when adding a new status it also has the "Any" transition. If that is different in your workflows then that is a deliberate decision. Wasn't the case as recently as 2020 (the last time I had access to create my own custom workflow, and I'm pretty sure that was a newer version of Jira than many large companies are using). Are you using the cloud version or something?
  - VonGallifrey 3y ago
    I am using the Cloud version, but I have been using Jira over the last 10~12 Years at different companies. I can't remember a time where transitions where restricted by default. I always preferred a less restricted workflow if I am working with a I can trust, but I can't remember needing to change workflows to enable transitions from a default. What I wanted to get across is that Jira makes it very easy to give control to the Team that is using a specific Board or Workflow. If your company don't trust their Teams with that then that is a failure of the company and not a failure of Jira.