Details
-
Suggestion
-
Resolution: Won't Do
-
None
Description
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
I recently read Sarah M and Bruces posts about using a task and subtasks as a clone template for repeated tasks.
And it got me thinking that we could offer variable replacement during clone to make it even more powerful.
In Sarahs examples she has Confluence X.X in each issue that she then needs to edit
What if we could replace them automatically
Something like ${version} becomes the value of a "version" variable at clone time.
I would change the clone dialog to allow a row of variable definitions. We could track those variables per person so they dont have to re-enter them over time.
This would make cloning even more powerful and powerful.
Attachments
Issue Links
- relates to
-
JRACLOUD-25037 IDEA : Variable replacement during clone
- Closed