It still requests that we upgrade to Jira Pro. For those who are interested, you can select "Project automation" from the Beam Project settings page or use this direct link https://issues.apache.org/jira/secure/AutomationProjectAdminAction!default.jspa?projectKey=BEAM
On Tue, Aug 27, 2019 at 5:20 AM Ismaël Mejía <[email protected]> wrote: > Apache's JIRA was updated recently. Luke (or someone else maybe) can > please help > me check if we still cannot create the rule to self triage the issues that > were > created and have already an assigned contributor. This will easily reduce > issue > triage to half because due to JIRA's UI it is really easy to forget to > self-triage the issues they create. > > Also a kind reminder to contributors and in particular current committers, > when > you create JIRAs, they are not automatically 'self-triaged' but in many > cases > they should be. Please take care to do the triage if it is already > assigned on creation or if you judge it is complete enough but prefer to > let it > unassigned in case someone else can work on it. That will for sure reduce > the > triage work until this becomes automatic. > > On Wed, Jun 12, 2019 at 6:16 PM Lukasz Cwik <[email protected]> wrote: > > > > I looked at automating the two in JIRA but got the unhelpful: > > > > "You are using Automation Lite for Jira. This is the free offering of > Automation for Jira Pro and only contains a small subset of the many > awesome features of the paid app. For example, project admins like yourself > can can only create and edit automation rules in the paid offering." > > > > On Wed, Jun 12, 2019 at 2:22 AM Ismaël Mejía <[email protected]> wrote: > >> > >> Kenn can you or someone else with more JIRA-fu than me automatize both > cases (I > >> just triaged most of the still untriaged issues and found multiple new > >> instances of > >> both cases). > >> > >> On Fri, Jun 7, 2019 at 10:27 PM Kenneth Knowles <[email protected]> > wrote: > >> > > >> > Nice. I noticed the huge drop in untriaged issues. Both of those > ideas for automation sound reasonable. > >> > > >> > I think the other things that are harder to optimize can probably be > addressed by re-triaging stale bugs. We will probably find those that > should have been closed and those that are just sitting on an inactive > contributor. > >> > > >> > Kenn > >> > > >> > On Fri, Jun 7, 2019 at 12:53 AM Ismaël Mejía <[email protected]> > wrote: > >> >> > >> >> I took a look and reduced the untriaged issues to around 100. I > >> >> noticed however some patterns that are producing more untriaged > issues > >> >> that we should have. Those can be probably automated (if JIRA has > ways > >> >> to do it): > >> >> > >> >> 1. Issues created and assigned on creation can be marked as open. > >> >> 2. Once an issue has an associated PR it could be marked as open if > it > >> >> was in Triaged state. > >> >> > >> >> Other common case that is probably harder to automate are issues that > >> >> are in Triaged state because we forgot to resolve/close them. I don’t > >> >> know how we can improve these, apart of reminding people to look that > >> >> they do not have untriaged assigned issues. > >> >> > >> >> Another interesting triage to do are the issues that are Open and > >> >> assigned to members of the community that are not active anymore in > >> >> the project, but that’s probably worth of another discussion, as well > >> >> as how can we more effectively track open unassigned issues (which > are > >> >> currently around 1600). > >> >> > >> >> On Wed, Jun 5, 2019 at 7:03 PM Tanay Tummalapalli < > [email protected]> wrote: > >> >> > > >> >> > Hi Kenneth, > >> >> > > >> >> > I already follow the issues@ mailing list pretty much daily. > >> >> > I'd like to help with triaging issues, especially ones related to > the Python SDK since I'm most familiar with it. > >> >> > > >> >> > On Wed, Jun 5, 2019 at 10:26 PM Alex Van Boxel <[email protected]> > wrote: > >> >> >> > >> >> >> Hey Kenneth, I help out. I'm planning to contribute more on Beam > and it seems to be ideal to keep up-to-date with the project. > >> >> >> > >> >> >> _/ > >> >> >> _/ Alex Van Boxel > >> >> >> > >> >> >> > >> >> >> On Wed, Jun 5, 2019 at 6:46 PM Kenneth Knowles <[email protected]> > wrote: > >> >> >>> > >> >> >>> Hi all, > >> >> >>> > >> >> >>> I am requesting help in triaging incoming issues. I made a > search here: https://issues.apache.org/jira/issues/?filter=12345682 > >> >> >>> > >> >> >>> I have a daily email subscription to this filter as a reminder, > but rarely can really sit down to do triage for very long. It has grown > from just under 200 to just over 200. The rate is actually pretty low but > there is a backlog. I also want to start re-triaging stale bugs but > priority would be (1) keep up with new bugs (2) clear backlog (3) re-triage > stale bugs. > >> >> >>> > >> >> >>> Just FYI what I look for before I clicked "Triaged" is: > >> >> >>> > >> >> >>> - correct component > >> >> >>> - correct priority > >> >> >>> - maybe ping someone in a comment or assign > >> >> >>> - write to dev@ if it is a major problem > >> >> >>> > >> >> >>> If I can't figure that out, then I ask the reporter for > clarification and "Start Watching" the issue so I will receive their > response. > >> >> >>> > >> >> >>> To avoid duplicate triage work it may help to assign to yourself > temporarily during triage phase. > >> >> >>> > >> >> >>> Any help greatly appreciated! > >> >> >>> > >> >> >>> Kenn >
