• 11
    • 32
    • Hide
      Atlassian Update – 16 February 2018

      Hi everyone,

      Thank you for your interest in this issue.

      While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status. 

      I understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, we've decided to prioritize other areas of the Jira Server roadmap, including:

      • Performance and stability improvements
      • Archiving projects for improved performance
      • Optimising the use of custom fields
      • Improving performance of boards
      • Improving Jira notifications
      • Allowing users to edit shared filters and dashboards
      • Mobile app for Jira Server

      We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.

      Meanwhile, for all customers who who need to bulk edit resolution, there is an existing workaround, which we know many of you have found useful.

      To learn more on how JAC suggestions are reviewed, see our updated workflow for server feature suggestions.

      Kind regards,

      Jira Server Product Management

      Show
      Atlassian Update – 16 February 2018 Hi everyone, Thank you for your interest in this issue. While this suggestion has gathered significant interest, we're unable to implement all of the excellent suggestions you make. We don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status.  I understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, we've decided to prioritize other areas of the Jira Server roadmap, including: Performance and stability improvements Archiving projects for improved performance Optimising the use of custom fields Improving performance of boards Improving Jira notifications Allowing users to edit shared filters and dashboards Mobile app for Jira Server We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here . Meanwhile, for all customers who who need to bulk edit resolution, there is an existing workaround , which we know many of you have found useful. To learn more on how JAC suggestions are reviewed, see our updated workflow for server feature suggestions . Kind regards, Jira Server Product Management
    • 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.

      A user asks:

      > Is there a quick way of bulk changing the resolution of issues in a
      > project? I basically forgot to include the "Resolve issue" screen from
      > our project's "Resolved" transition in the workflow, and there are
      > thus no resolutions for the recently resolved issues...

      Assuming that the user has the 'Resolve' and 'Edit' permissions, I can't see why the resolution shouldn't be editable.

      Workaround

      Please try the workaround listed here: HowTo: Bulk Edit Resolution

            [JRASERVER-7302] Bulk edit resolution

            I had many issues marked as 'Done' without a resolution because we weren't using the resolution field before.

            I set up an automation to run every 10 minutes to find 'Done' issues without a resolution and set their resolution to 'Done'.

            1. Trigger: Runs every 10 minutes. ( as I want them to change now)
            2. Condition: Look for 'Done' issues with no resolution in your project.
            3. Action: Sets the issue's resolution to 'Done'.

            This is a temporary setup. I'll remove it after all issues are updated. **

            sarah abd eldaym added a comment - I had many issues marked as 'Done' without a resolution because we weren't using the resolution field before. I set up an automation to run every 10 minutes to find 'Done' issues without a resolution and set their resolution to 'Done'. Trigger: Runs every 10 minutes. ( as I want them to change now) Condition: Look for 'Done' issues with no resolution in your project. Action: Sets the issue's resolution to 'Done'. This is a temporary setup. I'll remove it after all issues are updated.  **

            Chris added a comment -

            Just use Jira automation.

            Chris added a comment - Just use Jira automation.

            Bork added a comment -

            They'll never change this, as the hole has been plugged by marketplace entries like https://marketplace.atlassian.com/apps/1223455/advanced-bulk-edit-for-jira?tab=pricing&hosting=cloud and the toxic ecosystem will lock this in forever. It's nuts.

            Bork added a comment - They'll never change this, as the hole has been plugged by marketplace entries like https://marketplace.atlassian.com/apps/1223455/advanced-bulk-edit-for-jira?tab=pricing&hosting=cloud and the toxic ecosystem will lock this in forever. It's nuts.

            Derek White added a comment - The provided workaround doesn't even work: https://community.atlassian.com/t5/Jira-questions/Why-can-t-I-make-changes-on-my-DRAFT-workflow/qaq-p/782670

            I don't understand how something as basic as this is not being considered.  The suggested work arounds are ludicrous for anything substantial, the very thing this is needed for.  Buying an add-on for functionality that should already be included and supported is not an acceptable alternative.

            Bob Provencher added a comment - I don't understand how something as basic as this is not being considered.  The suggested work arounds are ludicrous for anything substantial, the very thing this is needed for.  Buying an add-on for functionality that should already be included and supported is not an acceptable alternative.

            Maybe right, but users cannot submit a request to administrators to operate change with Script Runner.
            Notice this app https://marketplace.atlassian.com/apps/1212611/bulk-operation-enhancer-for-jira?hosting=server&tab=overview provides a bulk operation to "Set Resolution field" to "regular users" BUT it is buggy from my point of view as "Resolution Date" is not properly set which may be a trouble for some reports or other apps - and so I had to fix field values with Script Runner by the way.

            Yves Martin added a comment - Maybe right, but users cannot submit a request to administrators to operate change with Script Runner. Notice this app https://marketplace.atlassian.com/apps/1212611/bulk-operation-enhancer-for-jira?hosting=server&tab=overview provides a bulk operation to "Set Resolution field" to "regular users" BUT it is buggy from my point of view as "Resolution Date" is not properly set which may be a trouble for some reports or other apps - and so I had to fix field values with Script Runner by the way.

            Bork added a comment -

            Sadly this will never get fixed as the facility is provided in paid plugins from third parties now. Most corporates just shell up for ScriptRunner which provides this.

            Bork added a comment - Sadly this will never get fixed as the facility is provided in paid plugins from third parties now. Most corporates just shell up for ScriptRunner which provides this.

            Kelly Cannon added a comment - - edited

            Update on this? Really would like to make a quick change and not have to change 28,000+ tickets one by one.

            Kelly Cannon added a comment - - edited Update on this? Really would like to make a quick change and not have to change 28,000+ tickets one by one.

            This is really needed. We have a number of issues that were flagged with a duplicate resolution that really should have been test issue resolution. It is critical that the resolved date remains as is so the transition workfaround will not work for us but we need to modify the resolution value to improve data quality for reporting.

            Denise Wermager added a comment - This is really needed. We have a number of issues that were flagged with a duplicate resolution that really should have been test issue resolution. It is critical that the resolved date remains as is so the transition workfaround will not work for us but we need to modify the resolution value to improve data quality for reporting.

            Is there a particular reason why this field is hidden during bulk edit in the first place?

             
            The workflow / scriptrunner workaround is needlessly cumbersome, and this is an issue I regularly encounter when I look at a new JIRA instance. Most project admins are comfortable editing workflows, but nobody sets them up properly to set the Resolution field. Until someone looks are the Created vs. Resolved charts...

            The default Kanban workflow also doesn't seem to care about this field. So if you're not helping users in keeping their data clean in the first place, at least give us an easy option to fix it after the fact!

            Christian Baerike added a comment - Is there a particular reason why this field is hidden during bulk edit in the first place?   The workflow / scriptrunner workaround is needlessly cumbersome, and this is an issue I regularly encounter when I look at a new JIRA instance. Most project admins are comfortable editing workflows, but nobody sets them up properly to set the Resolution field. Until someone looks are the Created vs. Resolved charts... The default Kanban workflow also doesn't seem to care about this field. So if you're not helping users in keeping their data clean in the first place, at least give us an easy option to fix it after the fact!

              Unassigned Unassigned
              7ee5c68a815f Jeff Turner
              Votes:
              366 Vote for this issue
              Watchers:
              171 Start watching this issue

                Created:
                Updated: