I'm aware of that, and that's currently what we are using. However, I'm not very happy of it.
When a job already has a long description, it makes the reason why it's disabled gets somewhere in the long description, it is more difficult to find. Also, the current UI doesn't encourage people to give a reason when they disable jobs whereas sharing why you disable a job is generally quite valuable.
Having it a text "Reason" field just after the "Disable Build" radio button would encourage people to share the reason why a build is disabled. On the main job page, we could read things such as "Job is currently disabled. Reason: It's a draft and is currently always failing".

So what you suggest works, but it's just a workaround IMHO.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to