Add condition to control when to create sub-tasks
This enhancement adds a conditional statement to the subtask creation post-function. Additional parameters have been added to the create/edit screen to configure the condition. Custom fields are enumerated and a select input is used to select the custom field to use as the condition. A text input is used to set the value that makes the condition true. Said custom field must be on the transition view screen and be set to the true condition during the transition (capture the rising edge from No to Yes, not just cf=Yes).
Due to how JIRA passes information around the location of the post-function in relation to the other post-functions matters. To mitigate this the enhancement compares a MutableIssue to the CustomField value AND inspects the transientVariables. This allows the post-function to be anywhere in the set of post-functions and still be accurate.
Not included but a useful addition would be a parameter to select "Edge Trigger" or "Field=Value" so the condition type is more flexible.
Conditional control has been added, however, the user interface and implementation is considerably different than indicated in the description. See [How to condition the creation of issues]
Yes, a form of conditioning is intended in the near future (< 30 days).
Hi all, is this a planned item to release soon I see lots of recent activity on this? I'm desperately trying to convince our IT department to upgrade JIRA in the hope that a new release of the CSOT plugin with creation conditions based of custom fields will be released. I see the code is done to a simple functionality so could this be packaged and released officially in the near future?
Would be nice if this feature would be implemented.
We need a control like "customfield="Yes" or component="jira" to create subtasks on transitions.
Good luck. I would like to add a value condition so that you can use an edge or a value for the condition but I haven't gotten around to it. If you find another solution please comment back so that I don't bother duplicating functionality.