Uploaded image for project: 'JIRA'
  1. JIRA
  2. JRA-13245

Bulk Convert Issues to Sub-task and back

    Details

    • Feedback Policy:

      JIRA feedback is collected from a number of different sources and is evaluated when planning the product roadmap. If you would like to know more about how JIRA Product Management uses customer input during the planning process, please see our post on Atlassian Answers.

      Description

      Atlassian Status as of 5 November 2014

      Hi everyone,

      Thanks so much for your votes and comments on this issue. We don't have plans to address this feature in the next 12 months, but this on our roadmap and we plan to address it in the future.

      In the meantime, there is one workaround provided by another customer which on premise customers can use.

      Thanks for your patience and we hope you appreciate our open approach to feature requests.

      Cheers,

      Bartek
      JIRA Product Management
      bartek (at) atlassian (dot) com

      Original request description

      In 3.9 JIRA introduced "Convert Issue to Sub-task" and "Convert Sub-task to Issue".
      It would be handy to be able to bulk convert.

        Issue Links

          Activity

          Hide
          martin.gregory Martin Gregory added a comment - - edited

          I recently filled out an Atlassian survey. I gave them 1/5 for "Atlassian listens". This is one of the examples of why.

          Show
          martin.gregory Martin Gregory added a comment - - edited I recently filled out an Atlassian survey. I gave them 1/5 for "Atlassian listens". This is one of the examples of why.
          Hide
          eoin.moloney Eóin Moloney added a comment -

          8 year.....

          Your description states not in the next 12 months I think you need to update the description to not in the next 96 months.

          Can you get this basic feature implemented please.

          Show
          eoin.moloney Eóin Moloney added a comment - 8 year..... Your description states not in the next 12 months I think you need to update the description to not in the next 96 months. Can you get this basic feature implemented please.
          Hide
          jarno.ahola2 Jarno Ahola added a comment -

          Huh, almost 8 years. I just bumped into this kind of problem. We have several hundreds of sub tasks to be converted to issues. Without this feature it's manual work for whole night for me... (not to mention that target issue type is Epic, which causes extra work to set mandatory Epic Name field, even with bulk change that would be pain in the... you know).

          Anyway, this feature is really needed. Almost 8 years is too long time to wait. This shouldn't be too complex to implement? Please Atlassian, pimp our JIRAs with this feature.

          Show
          jarno.ahola2 Jarno Ahola added a comment - Huh, almost 8 years. I just bumped into this kind of problem. We have several hundreds of sub tasks to be converted to issues. Without this feature it's manual work for whole night for me... (not to mention that target issue type is Epic, which causes extra work to set mandatory Epic Name field, even with bulk change that would be pain in the... you know). Anyway, this feature is really needed. Almost 8 years is too long time to wait. This shouldn't be too complex to implement? Please Atlassian, pimp our JIRAs with this feature.
          Hide
          alan.sigus Alan Sigus added a comment -

          Really need it. Projects are changing through time, people change the way they work, start using agile, epics and all that. Sometimes subtasks need to be converted to issues. Project changes under new management etc.
          Currently, I need to change 500+ subtasks into issues. Why I have to look into ways to trick the GUI to click through the conversion process if this should be made as simple as bulk change.

          This problem won't go away with time, Atlassian, it only gets worse. Don't ignore it.

          Show
          alan.sigus Alan Sigus added a comment - Really need it. Projects are changing through time, people change the way they work, start using agile, epics and all that. Sometimes subtasks need to be converted to issues. Project changes under new management etc. Currently, I need to change 500+ subtasks into issues. Why I have to look into ways to trick the GUI to click through the conversion process if this should be made as simple as bulk change. This problem won't go away with time, Atlassian, it only gets worse. Don't ignore it.
          Hide
          jelena.radovanovic Jelena Radovanovic added a comment -

          Hello,

          I have the same problem, batch of tickets that should be converted into sub-task or into task.
          However, if you have admin rights, as a currently solution you could use groovy script.
          Groovy solved problem for me..

          Show
          jelena.radovanovic Jelena Radovanovic added a comment - Hello, I have the same problem, batch of tickets that should be converted into sub-task or into task. However, if you have admin rights, as a currently solution you could use groovy script. Groovy solved problem for me..

            People

            • Assignee:
              Unassigned
              Reporter:
              nick.menere Nick Menere [Atlassian]
            • Votes:
              382 Vote for this issue
              Watchers:
              192 Start watching this issue

              Dates

              • Created:
                Updated: