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

Please add the ability to move an issue between projects to the rest api.

XMLWordPrintable

    • 36
    • 10

    • 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.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.

      Currently it is not possible to move an issue from one project in JIRA to another project using the rest api. Please add the ability to move an issue between projects to the rest api.

            [JRACLOUD-61359] Please add the ability to move an issue between projects to the rest api.

            Dave Furlani added a comment -

            Pretty sure this is a duplicate of https://jira.atlassian.com/browse/JRACLOUD-70305

            Dave Furlani added a comment - Pretty sure this is a duplicate of https://jira.atlassian.com/browse/JRACLOUD-70305

            David Pezet added a comment -

            I think this would be great, even if it only worked when the projects are using all the same necessary configuration schemes. That way when there are several Company Managed projects all using the same configurations, issues could move freely between them. If it can't exist as-is in the new project, then return an error, or maybe then allow passing in the values to let it fit, but I think just moving 1:1 would be incredibly nice.

            David Pezet added a comment - I think this would be great, even if it only worked when the projects are using all the same necessary configuration schemes. That way when there are several Company Managed projects all using the same configurations, issues could move freely between them. If it can't exist as-is in the new project, then return an error, or maybe then allow passing in the values to let it fit, but I think just moving 1:1 would be incredibly nice.

            Christophe Noualhat added a comment -

            Even moving an issue from one task type to another (subtask to task) causes major problems.

            If changing the issue type from as subtask type to a task type is done using an automation script, the task type is changed but Jira still considers the new issue type (task) as a subtask and keeps the link to the existing parent as before, thus creating inconsistencies where issues of type task are considered childs of another issue of type task...

            Christophe Noualhat added a comment - Even moving an issue from one task type to another (subtask to task) causes major problems. If changing the issue type from as subtask type to a task type is done using an automation script, the task type is changed but Jira still considers the new issue type (task) as a subtask and keeps the link to the existing parent as before, thus creating inconsistencies where issues of type task are considered childs of another issue of type task...

            alexmin (Inactive) added a comment -

            Can we use default value which used in the UI?

            alexmin (Inactive) added a comment - Can we use default value which used in the UI?

            David Black added a comment -

            That's a good question and I don't have a good answer for that right now.

            David Black added a comment - That's a good question and I don't have a good answer for that right now.

            MattS added a comment -

            David, how would you suggest providing the mapping information that JIRA walks you through in the UI

            MattS added a comment - David, how would you suggest providing the mapping information that JIRA walks you through in the UI

              Unassigned Unassigned
              dblack David Black
              Votes:
              27 Vote for this issue
              Watchers:
              20 Start watching this issue

                Created:
                Updated: