The management of sub-tasks in the "Create sub-tasks" automation action works well for initial rule creation, but if changes are needed after the rule is first published, then it quickly spirals into an untenable situation, often requiring rules developers to recreate the rule from scratch for each change in order to maintain a given rule to the standards set by project leads.

As a user, I would like to be able to accomplish the following within the "Create Sub-tasks" action (and within any other similar rules to which this could apply):

• Be able to sort, either by predefined criteria (alphabetical, etc), or manually. This ensures consistency in matching sub-task to defined and evolving team procedures.
• Be able to manage fields for sub-tasks in a batch fashion, without each change pulling the individual sub-tasks out into separate rules.