It would be nice if the greenhopper default workflows could be made read-only like the JIRA default workflow. A text note about not editing them is not sufficient. Thoughts?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Actually that warning message is slightly mis-leading, you are right. But it achieves what it is meant for, scare off people who do not know what that workflow is for and those who know that it can be customized, will do it with care :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.