Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JRACLOUD-25037

IDEA : Variable replacement during clone

    XMLWordPrintable

Details

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

    Description

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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

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

              Dates

                Created:
                Updated:
                Resolved: