3 ms·

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 ne

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

> 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.