What is the difference between resolving an issue vs closing the issue? Do we need that extra step of closing an issue?
On Fri, Feb 19, 2021 at 2:05 AM Alexandre Rafalovitch <[email protected]> wrote: > You may enjoy using JiraSearch for this kinds of things, it has a very > nice "Updated Ago >x", and "Last comment user" facet and 'shift-click' > multi-select on status: > http://jirasearch.mikemccandless.com/ > > For the bulk changes, from the screen you are at, you click on Tools > near top-right area of the screen and select "screen" or "1000" and > that's the beginning of the process. Makes sure to unselect "notify > everybody" box on the last (2nd last?) screen or a lot of people will > be upset. > > But also, we had less than fantastic history with bulk closing (had to > reopen/revert). So, it may be better to focus on a very small, clearly > "done" subset and/or leave quick notes "can this be closed" with a > follow-up to close. > > Regards, > Alex. > > On Thu, 18 Feb 2021 at 14:43, Eric Pugh <[email protected]> > wrote: > > > > I’m still learning my way around JIRA, and I was looking for a Solr JIRA > that I swear I had seen open recently. In trying to query for open/active > JIRAs, I crafted this query, which returned a lot of tickets that I *think* > should be CLOSED at this point: > > > > > https://issues.apache.org/jira/browse/SOLR-13394?jql=project%20%3D%20SOLR%20AND%20status%20in%20(Open%2C%20Reopened%2C%20Resolved%2C%20%22Patch%20Available%22)%20AND%20resolution%20%3D%20Fixed%20AND%20fixVersion%20in%20releasedVersions() > > > > There are 1102 tickets that appear to be old dealt with tickets and > should be CLOSED. > > > > I wanted to point that out, and see if someone could move them to > CLOSED, or point me to how to do the Bulk Close that I’ve seen happen > periodically over the years. > > > > Eric > > > > _______________________ > > Eric Pugh | Founder & CEO | OpenSource Connections, LLC | 434.466.1467 | > http://www.opensourceconnections.com | My Free/Busy > > Co-Author: Apache Solr Enterprise Search Server, 3rd Ed > > This e-mail and all contents, including attachments, is considered to be > Company Confidential unless explicitly stated otherwise, regardless of > whether attachments are marked as such. > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
