On demand / Cloud Sub-Task transition automation?

[Justin Sloan]

We are evaluating a move off of JIRA Cloud as we cannot determine a repeatable way to manage subtasks in the cloud environment. 

• Create on transition - No plugins available in cloud
• Transition Parent based on Sub-task transition - Post Functions - Not always successfully executed and no access to error logs to troubleshoot?
• Transition Sub-task based on Parent transition - Post Functions - Not always successfully executed and no access to error logs to troubleshoot?

Any suggestions or patterns that have worked for your organizations?

[GabrielleJ]

My top 5 choices for customizing my JIRA workflows and process to my hearts content are:

• JIRA Misc Workflow https://marketplace.atlassian.com/plugins/com.innovalog.jmwe.jira-misc-workflow-extensions/cloud/overview
• JIRA Suite Utlities https://marketplace.atlassian.com/plugins/com.googlecode.jira-suite-utilities/cloud/overview
• JIRACLI https://marketplace.atlassian.com/plugins/org.swift.jira.acli/server/overview
• JIRA ScriptRunner https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner/server/overview

*Not in particular order 

[Nic Brough -Adaptavist-]

I tend to skip JMWE if ScriptRunner is available  

[Justin Sloan]

Bob thank you for the note I have added a comment to your linked article we certainly would be interested in participating.  That item alone is one of our largest drivers to exit ondemand/cloud 

[Bob Swift OSS (Bob Swift Atlassian Apps)]

Regarding your first bullet, that is in progress: CSOT-136.