We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

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

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.

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

                        Unassigned Unassigned
                        77372462e2ff alajangi santosh kumar
                        Votes:
                        8 Vote for this issue
                        Watchers:
                        4 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            77372462e2ff alajangi santosh kumar
                            Votes:
                            8 Vote for this issue
                            Watchers:
                            4 Start watching this issue

                              Created:
                              Updated: