There is a 'Triaged' button that I click: https://photos.app.goo.gl/Ub5Qwnpp6aFrmaDZ9
On Mon, Mar 15, 2021 at 9:48 AM Alex Amato <ajam...@google.com> wrote: > (Do I need certain permissions to be able to do this?) > > On Mon, Mar 15, 2021 at 9:47 AM Alex Amato <ajam...@google.com> wrote: > >> Would you mind posting a screenshot of exactly where you are supposed to >> click to move a jira issue to "Open" status? I honestly can't find where to >> click. I don't see the option in the edit dialog box >> >> On Sun, Mar 14, 2021 at 8:03 PM Kenneth Knowles <k...@apache.org> wrote: >> >>> No need for feeling any guilt :-) >>> >>> I'm just hoping that by everyone randomly doing a very small amount of >>> work, this could be in good shape very quickly. I've done a number of bulk >>> edits like automated dependency upgrade requests which brings the number >>> down to just over 600. >>> >>> Your message does highlight some easy cases: issues filed to track your >>> own feature work. I did built automation for this: "On Issue Created" -> >>> "If Assignee == Issue Creator" -> "Transition to 'Open'". If the automation >>> isn't working, that can probably be fixed. Some of the issues might just >>> predate the automation. >>> >>> To be super clear: I don't mean to ask anyone to waste time looking at >>> things that don't need attention, but to be able to notice things that do >>> need attention. I did a few manually too, and the components, issue type, >>> and priority very often need fixing up. I especially want to get untriaged >>> P0s and P1s to zero. >>> >>> Kenn >>> >>> On Fri, Mar 12, 2021 at 5:07 PM Tyson Hamilton <tyso...@google.com> >>> wrote: >>> >>>> I'm guilty of creating issues and not moving them to 'open'. I'll do >>>> better to move them to open in the future. To recompense I will spend some >>>> additional time triaging =) >>>> >>>> Thanks for the review of the flow. >>>> >>>> On Thu, Mar 11, 2021 at 12:39 PM Kenneth Knowles <k...@apache.org> >>>> wrote: >>>> >>>>> Hi all, >>>>> >>>>> You may or may not think about this very often, but our Jira workflow >>>>> goes like this: >>>>> >>>>> Needs Triage --> Open --> In Progress --> Resolved >>>>> >>>>> "Needs Triage" means someone needs to look at it briefly: >>>>> >>>>> - component(s) >>>>> - label(s) >>>>> - issue type >>>>> - priority (see https://beam.apache.org/contribute/jira-priorities/) >>>>> - if appropriate, ping someone or write to dev@ especially for P1 >>>>> and P0 >>>>> >>>>> Then transition the issue to "Open". >>>>> >>>>> Currently there is a big backlog but I don't think it is actually >>>>> accurate. I also think we have enough people to keep up with this and even >>>>> to eliminate the backlog pretty quick. >>>>> >>>>> Here are some things you can do when you are waiting for Jenkins tests >>>>> to complete: >>>>> >>>>> - check your assigned issues >>>>> - open up this filter and triage a couple issues at random: >>>>> https://issues.apache.org/jira/issues/?filter=12345682 >>>>> >>>>> 800+ may seem like a lot, but dev@ had 65 participants in the last 28 >>>>> days (126 participants in the last 3 months). I would guess it averages >>>>> less than a minute per issue so this could be done in less than a day, >>>>> especially considering our CI times :-) >>>>> >>>>> Kenn >>>>> >>>>>
