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

      Summary

      Updating / Editing / Deleting multiple issues in one bulk REST API request.

      Background

      Our product provides users with Gantt chart that synchronizes Gantt task start/end date with Jira issue date fields. Moving task with dependencies on Gantt recalculates start/end dates of dependent tasks and synchronizes them back to JIRA.
      Consequently moving single task on Gantt may result in an update of hundreds of issues.
      This is a common scenario in our product.

      Bulk issue update would improve the user experience of our product, therefore made it more attractive to enterprise customers with lots of tasks in project portfolios.

            [JRACLOUD-70356] Bulk issue edit REST API

            Pinned comments

            Hello Everyone, we’re thrilled to announce that Bulk Edit REST API (Beta) is available for public use. You can now create your own use cases, create automations & update issues in bulk using this API.

            For more details, you can visit the community group - https://community.atlassian.com/t5/Bulk-Ops-APIs-Beta-articles/Bulk-Edit-and-Bulk-Move-APIs-Beta-are-here/ba-p/2728954

            Mandeep Singh (Inactive) added a comment - Hello Everyone, we’re thrilled to announce that Bulk Edit REST API (Beta) is available for public use. You can now create your own use cases, create automations & update issues in bulk using this API. For more details, you can visit the community group - https://community.atlassian.com/t5/Bulk-Ops-APIs-Beta-articles/Bulk-Edit-and-Bulk-Move-APIs-Beta-are-here/ba-p/2728954

            All comments

            Patience is a virtue. The ones who can wait are the ones who get what's worth having.

            Bartłomiej Janczak {Appfire} added a comment - Patience is a virtue. The ones who can wait are the ones who get what's worth having.

            Apologies for the confusion - this was meant to be closed as it rolled out in July. 

            Melanie Coogan (Inactive) added a comment - Apologies for the confusion - this was meant to be closed as it rolled out in July. 

            Pete Dunham added a comment - - edited

            Pete Dunham added a comment - - edited 79bed106a576 this appears to be live: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-bulk-operations/#api-rest-api-3-bulk-issues-fields-get and the docs are not marked as experimental.  This seems to align with previous comments and https://community.atlassian.com/t5/Bulk-Ops-APIs-Beta-articles/Bulk-Edit-and-Bulk-Move-APIs-Beta-are-here/ba-p/2728954 Is Atlassian rolling this back?

            Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future. Bulk edit is used to update a set of fields/values across the given list of issues, not individuals unique edits. The APIs behave the same way as the UI from backlog. 

            Please remember that jira.atlassian.com is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through Atlassian Community. Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog.

            We understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions or feedback.

            Mel

            Senior Product Manager 

            Melanie Coogan (Inactive) added a comment - Thank you for raising and voting on this suggestion. Your feedback is invaluable in shaping and enhancing Jira for all users. Given the high volume of feature suggestions for Jira, we must prioritize those that provide the most value to the majority of our users. After a thorough review by the team, we have decided that we will not be able to implement this suggestion in the immediate future. Bulk edit is used to update a set of fields/values across the given list of issues, not individuals unique edits. The APIs behave the same way as the UI from backlog.  Please remember that  jira.atlassian.com  is only one of many inputs for our roadmap. We’re continuously learning, analysing and interviewing customers to make Jira better. We encourage you to also share your feedback through  Atlassian Community . Please also check out latest updates and upcoming plans from the Jira Cloud roadmap and the Atlassian Cloud release notes blog . We understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions or feedback. Mel Senior Product Manager 

            Ricardo Martinez added a comment - - edited

            Hi 97cbdc410d11 

             

            Is it possible to Transition in Bulk?

            Ricardo Martinez added a comment - - edited Hi 97cbdc410d11     Is it possible to Transition in Bulk?

            Many users are asking for the ability to have values specific to issues and not the same value for all issues. What's been implemented is the ability to edit the same set of fields, with the very same value, for up to 1000 in a shot. Of course, we can keep both functionalities.

            What we’re specifically looking for is the ability to have, say 1000 issues, each one with its own set of modified fields and values, in the bulk edit payload. Just like it is done for entity properties if I’m not wrong.

            Hervé Mutombo added a comment - Many users are asking for the ability to have values specific to issues and not the same value for all issues. What's been implemented is the ability to edit the same set of fields, with the very same value, for up to 1000 in a shot. Of course, we can keep both functionalities. What we’re specifically looking for is the ability to have, say 1000 issues, each one with its own set of modified fields and values, in the bulk edit payload. Just like it is done for entity properties if I’m not wrong.

            Second, the previous comments: would really prefer the ability to submit different values for each issue.

            Khari Gardner added a comment - Second, the previous comments: would really prefer the ability to submit different values for each issue.

            I was really expecting to be able to bulk update multiple issues with different values on multiple fields. It looks like this just gives you the ability to update multiple issues with the same field values

            Walter King added a comment - I was really expecting to be able to bulk update multiple issues with different values on multiple fields. It looks like this just gives you the ability to update multiple issues with the same field values

            Hi 97cbdc410d11 :

            Is it possible to bulk edit issues and each issue setting with different field value.

            e.g: Editing two issues

            Issue 1: Remaining Time Estimate 8h / Assignee: abc etc..

            Issue 2: Remaining Time Estimate 10h / Assignee: xyz etc...

             

            Thanks in advance!

            shashank chandra added a comment - Hi 97cbdc410d11 : Is it possible to bulk edit issues and each issue setting with different field value. e.g: Editing two issues Issue 1: Remaining Time Estimate 8h / Assignee: abc etc.. Issue 2: Remaining Time Estimate 10h / Assignee: xyz etc...   Thanks in advance!

            Hello Everyone, we’re thrilled to announce that Bulk Edit REST API (Beta) is available for public use. You can now create your own use cases, create automations & update issues in bulk using this API.

            For more details, you can visit the community group - https://community.atlassian.com/t5/Bulk-Ops-APIs-Beta-articles/Bulk-Edit-and-Bulk-Move-APIs-Beta-are-here/ba-p/2728954

            Mandeep Singh (Inactive) added a comment - Hello Everyone, we’re thrilled to announce that Bulk Edit REST API (Beta) is available for public use. You can now create your own use cases, create automations & update issues in bulk using this API. For more details, you can visit the community group - https://community.atlassian.com/t5/Bulk-Ops-APIs-Beta-articles/Bulk-Edit-and-Bulk-Move-APIs-Beta-are-here/ba-p/2728954

              79bed106a576 Melanie Coogan (Inactive)
              a21d157266aa Bartłomiej Jańczak [SoftwarePlant]
              Votes:
              665 Vote for this issue
              Watchers:
              205 Start watching this issue

                Created:
                Updated:
                Resolved: