I am guessing you are talking about the simplied workflow of GreenHopper.
There seems to be issue here since many cases users needs to customize those workflows to set custom postfunctions, for example, setting a resolutions, triggering builds, notifying hipchat etc. If it is made readonly, then users will not be able to do it.
While I agree that it is a very valid point for example for custom fields and there is something coming soon - https://jira.atlassian.com/browse/GHS-6152
Yes, that's what I'm referring to. I guess I was confused a little by how the workflow is generated. It appears that a new workflow is created for each project. The workflow has the following description "Generated by GreenHopper version 6.1.2. This workflow is managed internally by GreenHopper. Do not manually modify this workflow." which could be a bit misleading unless there is some credible reason like it would break upgradability. If that's the case, it would be in conflict with your answer. If there is no inherent harm in modifying a greenhopper workflow, then the description should be changed.
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs