Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-42307

Automatically Edit 1000 Issues Continuously if Issues to be Edited is more than 1000

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • None
    • None
    • 2
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

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

      Currently, JIRA have been limiting "Bulk Edit" to only 1000 issues. While there might be a reason for the limitation such as it might able to impact the instance performance, there is no tool or other workaround to differentiate the previous edited 1000 issues if the issues that needs to be edited is more than 1000. While JIRA Admin able to make changes on the field to mark issues that have been edited, it will always be two steps operation:

      1. Bulk Edit and update fields to mark it while making the actually changes.
      2. Do another search with "!=" expression or JQL search that could differentiate it.
      3. Repeat.

      These operation will take longer and major work to do if the issues need to be edited for example about 10,000, not to mention there could be a human error where the previous issues is included inside.

      Hence, it would be great if there is a Tool or function that could segregated the 1000 issues out of 10,000 then runs automatically until those 10,000 issues is edited, rather than repeating the operation above again and again,

          Form Name

            [JRASERVER-42307] Automatically Edit 1000 Issues Continuously if Issues to be Edited is more than 1000

            Atlassian Update – 15 March 2018

            Hi,

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance.

            For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence.

            Thanks again.
            Regards,
            Jira Product Management

            Gosia Kowalska added a comment - Atlassian Update – 15 March 2018 Hi, Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. For more context, check out our Community blog on our renewed approach to highly voted Server suggestions for Jira and Confluence . Thanks again. Regards, Jira Product Management

            Hello,
            This is a major issue for me too.
            Cheers,
            JG

            JG Meillaud added a comment - Hello, This is a major issue for me too. Cheers, JG

              Unassigned Unassigned
              jrahmadiputra Julian (Inactive)
              Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: