Uploaded image for project: 'Jira Server and Data Center'
  1. Jira Server and Data Center
  2. JRASERVER-25037

IDEA : Variable replacement during clone

    XMLWordPrintable

    Details

    • Feedback Policy:
      We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      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.

      http://ffeathers.wordpress.com/2011/04/12/jira-cloning-to-create-a-template-for-repeated-documentation-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

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              bbaker ɹǝʞɐq pɐɹq
              Votes:
              10 Vote for this issue
              Watchers:
              9 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: