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 2 September 2015

      Hi everyone,

      Thanks so much for your votes and comments on this issue.

      Good news - this request was successfully implemented.

      For those of you who are using the JIRA Cloud, the feature was rolled out on 24th of August. For JIRA Server users - please expect this feature to be delivered with the upgrade to JIRA 7.0 - planned to be released shortly.

      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.

        Attachments

          Issue Links

            Activity

            Hide
            kontakt3 Martin added a comment -

            I did not get this to work on Jira 7 hosted on our own server.

            Just upgraded

            Show
            kontakt3 Martin added a comment - I did not get this to work on Jira 7 hosted on our own server. Just upgraded
            Hide
            kontakt3 Martin added a comment -

            Works again now.
            (perhaps by checking the box "Use the above project and issue type pair for all other combinations.")

            Show
            kontakt3 Martin added a comment - Works again now. (perhaps by checking the box "Use the above project and issue type pair for all other combinations.")
            Hide
            denis.yaparov@gmail.com Denis Yaparov added a comment -

            For those, who is still on Jira 6.4 here is another workaround for massive convert from sub-task to standard issue type. Please, find attached file DYConvertSubIssueToIssue.zip. It is based on Matthias Hößl's solution, but much easier to use.
            Usage:
            1. Get target issue type's ID. For example, from URL "Edit" against required issue type on "Issue Types" admin page.
            2. Unzip, open & copy script text to buffer
            3. Open Issue Navigator and enter JQL to find all sub-issues to convert (you may start from 1 issue by adding 'and issuekey = PRJ-111' at the end of JQL). Script will take jql string from URL bar (param ?jql=...).
            4. Open developer tools -> Console, paste scripts' code. Edit target issue type ID in first lines.
            5. Run script. It should show issue keys and Step OK four times each issue.

            Limitations:
            1. Target issue type shouldn't have additional requires fields. Existing subissues should have all required fields filled.
            2. "Step is OK" mark actually means nothing, it just states, that Jira's returned HTTP code 200 on request. Check Issue Navigator after script finished. If an issue wasn't converted, try to convert it manually, may be one of required fields is empty.
            3. Script expects, that base Url is configured correctly.
            4. Jira creates unique wizard's ID for each issue. It can prevent immediate re-run of the script.

            Tested on:
            Jira 6.4
            IE 11

            Show
            denis.yaparov@gmail.com Denis Yaparov added a comment - For those, who is still on Jira 6.4 here is another workaround for massive convert from sub-task to standard issue type. Please, find attached file DYConvertSubIssueToIssue.zip . It is based on Matthias Hößl's solution, but much easier to use. Usage: 1. Get target issue type's ID. For example, from URL "Edit" against required issue type on "Issue Types" admin page. 2. Unzip, open & copy script text to buffer 3. Open Issue Navigator and enter JQL to find all sub-issues to convert (you may start from 1 issue by adding 'and issuekey = PRJ-111' at the end of JQL). Script will take jql string from URL bar (param ?jql=...). 4. Open developer tools -> Console, paste scripts' code. Edit target issue type ID in first lines. 5. Run script. It should show issue keys and Step OK four times each issue. Limitations: 1. Target issue type shouldn't have additional requires fields. Existing subissues should have all required fields filled. 2. "Step is OK" mark actually means nothing, it just states, that Jira's returned HTTP code 200 on request. Check Issue Navigator after script finished. If an issue wasn't converted, try to convert it manually, may be one of required fields is empty. 3. Script expects, that base Url is configured correctly. 4. Jira creates unique wizard's ID for each issue. It can prevent immediate re-run of the script. Tested on: Jira 6.4 IE 11
            Hide
            rhoran Robert Horan added a comment -

            So Denis, in order to use this solution one must have Script Runner? You also mention those not on 7. Is this solved in 7?

            Show
            rhoran Robert Horan added a comment - So Denis, in order to use this solution one must have Script Runner? You also mention those not on 7. Is this solved in 7?
            Hide
            denis.yaparov@gmail.com Denis Yaparov added a comment - - edited

            Hi Robert,
            No, this is pure javascript code, only modern browser with developer tools is required. Actually, it emulates 'Convert to Issue' wizard from "More Actions" dropdown menu, just as an user clicks buttons using its mouse.
            I've tested it only with IE 11 and Jira 6.4.
            Yes, it looks like it should be fixed in Jira 7.0, because this issue is resolved with Fix Version/s = 7.0.0.

            Show
            denis.yaparov@gmail.com Denis Yaparov added a comment - - edited Hi Robert, No, this is pure javascript code, only modern browser with developer tools is required. Actually, it emulates 'Convert to Issue' wizard from "More Actions" dropdown menu, just as an user clicks buttons using its mouse. I've tested it only with IE 11 and Jira 6.4. Yes, it looks like it should be fixed in Jira 7.0, because this issue is resolved with Fix Version/s = 7.0.0.

              People

              • Assignee:
                Unassigned
                Reporter:
                nick.menere Nick Menere [Atlassian] (Inactive)
              • Votes:
                413 Vote for this issue
                Watchers:
                226 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: