Our organization deploys applications that consist of many components to a number of environments. Each deployment of an application to a specific environment is documented in a Jira ticket called an RFD. An RFD consists of a number of subtasks, each of which is the deployment of one component.

The easiest way to create an RFD for an application version deployment into an environment other than the first is to clone the "previous" RFD (the one from the next lower environment.) This is a very useful feature of JIRA, but it could be a lot more useful if it had the following characteristics:

1. When cloning an RFD and its subtasks, do NOT prefix the title with "CLONE - ". This just makes work, as each has to be edited, individually, to remove this text.
2. A "Clone" link should be created from each subtask to the subtask from which it was cloned. So not only is there a Clone relationship between the cloned RFD and the original, there's one between each subtask of the cloned RFD and its original. This makes navigating between subtasks much quicker.

Often RFDs are created from portions of RFDs for previous application deployments. This requires cloning the RFD of the previous version, but since we don't want all subtasks to be cloned (since they can't be deleted) we are forced to then clone those subtasks of the original that we need in the clone. This must be done individually. Each must then be moved and edited (to remove "CLONE - "). I would love to see:

1. Cloning of subtasks be a bulk operation
2. When cloning subtasks, allow the user to select a new parent at that time.
3. If a new parent is selected, do not prefix the cloned subtask's title with "CLONE - "
4. Create a link from the cloned subtask to the original as in (2) above.

Thanks for listening and wow if you could implement these feature it would save me hours.