Hello everyone, `Component` & `Affects version` are required fields when filing Airflow Jira issues now. Could you please help me test it and confirm that it is working as desired?
Thanks Aizhamal On Wed, May 22, 2019 at 11:01 PM Jarek Potiuk <jarek.pot...@polidea.com> wrote: > I think we indeed need to do some minimal and as automated as possible > "triage" process in place and having some JIRA automation around it would > be great. > > I think it's something that Ash after he returns from his holidays > mentioned that he would like to take care about - especially with the > upcoming 2.0 release. With the number of committers we have now, I think we > need to organise it a bit. I am happy to help with discussing the process > and taking part in introducing it. > > J. > > On Tue, May 21, 2019 at 8:36 PM Aizhamal Nurmamat kyzy > <aizha...@google.com.invalid> wrote: > > > Hi Fokko, > > > > Sid gave me the admin rights yesterday, forgot to update here. Thank you. > > > > I have edited the components themselves, but to make components the > > required filed I need to ask Infra. I created this ticket [1], still > > waiting for it to be resolved. > > > > Wouldn't it be smarter that users won't tag labels/component themselves? > > > Any new ticket will get "triage" tag and once the community review the > > > request they will set the proper components/priority ? > > > > > > Users can easily tag the wrong components so it's likely that the > ordered > > > Jira we have now won't stay like this for long. > > > > > > > Asking users to add the components by themselves may add some noise to > the > > triage process, but it should reduce the workload on maintainers, > triagers, > > and others tracking specific areas of the project. Although at the moment > > it's not possible to know for sure if an issue has been triaged or not, > we > > can move to a process that clearly marks untriaged issues as such, and > > maintainers will be able to look at an issue, and add/remove any > > components/labels if necessary. > > > > At the moment there are ~400 issues without any components added. I’ll go > > through them and try to give them a component; but this sort of “issue > > lake” can easily become forgotten. We also can’t ensure/force maintainers > > to always do triage of issues filed in this lake. > > > > Another reason to have issues filed with a component is because there are > > parties that care and track only certain components, and for them it is > > hard to discover all the issues. > > > > In other apache projects, the triage process relies on a Jira workflow > that > > goes "Triage Needed" -> "Open" -> "Resolved/Closed" (see possible jira > > statuses [2]). This automatically marks new issues in a “Triage Needed” > > status. I’d like to discuss this process after we’re done making the > > changes proposed in this document. > > > > Let me know what you all think. > > > > Thanks, > > Aizhamal > > > > [1] https://issues.apache.org/jira/browse/INFRA-18410 > > [2] https://issues.apache.org/jira/ShowConstantsHelp.jspa > > > > > > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > > On Tuesday, May 21, 2019 11:25 AM, Driesprong, Fokko > > <fo...@driesprong.frl> > > > wrote: > > > > > > > Hi Aizhamal, > > > > > > > > Sorry for the late reply. You're still an administrator on the Jira. > > > Please let me know if you're missing any privileges. > > > > > > > > Cheers, Fokko > > > > > > > > Op za 18 mei 2019 om 05:24 schreef Aizhamal Nurmamat kyzy > > > <aizha...@google.com.invalid>: > > > > > > > >> Hello everyone, > > > >> it took me longer than expected, but I finally got around to making > > > these > > > >> changes. I've moved all the issues to rightful components (except > for > > > those > > > >> lacking any component - I'll work on those afterwards). > > > >> I think I am unable to make changes to the components themselves > > > (renames / > > > >> deletes). Fokko, or anyone in the PMC, would you be able to grant me > > the > > > >> privileges once more? My username is aizhamal. I'd like to do this > as > > > soon > > > >> as possible, so that I won't have to clean up issues added to > > components > > > >> that are to be removed. > > > >> > > > >> Thanks a lot! I'll notify you on this thread once I have done the > > > changes > > > >> to components. :) > > > >> > > > >> Aizhamal > > > >> > > > >> On Fri, May 10, 2019 at 2:10 PM Aizhamal Nurmamat kyzy < > > > aizha...@google.com> > > > >> wrote: > > > >> > > > >>> Thank you for Jira powers, Fokko :) I am aiming to get it done by > > > Monday. > > > >>> > > > >>> Regards, > > > >>> Aizhamal > > > >>> > > > >>> *From: *Driesprong, Fokko <fo...@driesprong.frl> > > > >>> *Date: *Fri, May 10, 2019 at 4:05 AM > > > >>> *To: * <dev@airflow.apache.org> > > > >>> *Cc: *Siddharth Anand, airflowuser > > > >>> > > > >>> Hi Aizhamal, > > > >>>> > > > >>>> Great suggestions. The Jira needs some love. I've added you to the > > > >>>> administrator group. Let me know if there are any issues. > > > >>>> > > > >>>> Cheers, Fokko > > > >>>> > > > >>>> Op ma 6 mei 2019 om 20:28 schreef Aizhamal Nurmamat kyzy > > > >>>> <aizha...@google.com.invalid>: > > > >>>> > > > >>>> > Hello all, > > > >>>> > > > > >>>> > If it's okay by everyone, I would like to start performing the > > > changes > > > >>>> > outlined in the doc. +Siddharth Anand <san...@apache.org> could > > you > > > >>>> grant > > > >>>> > me the pertinent privileges to Airflow JIRA? Once you grant me > > > those, I > > > >>>> > will also have Bulk Change permission[1] to make those changes > > > faster. > > > >>>> > > > > >>>> > I will perform the changes, and notify this thread once it's > done. > > > >>>> > > > > >>>> > Thank you, > > > >>>> > Aizhamal > > > >>>> > > > > >>>> > [1] https://issues.apache.org/jira/browse/INFRA-18338 > > > >>>> > > > > >>>> > *From: *Jarek Potiuk <jarek.pot...@polidea.com> > > > >>>> > *Date: *Fri, May 3, 2019 at 5:31 AM > > > >>>> > *To: * <dev@airflow.apache.org> > > > >>>> > *Cc: *airflowuser > > > >>>> > > > > >>>> > +1 on mandatory component. +1 on mandatory version. I like the > > > proposed > > > >>>> > > cleanup suggestions. > > > >>>> > > > > > >>>> > > According to this discussion: > > > >>>> > > > > > >>>> > > > > > >>>> > > > > >>>> > > > > > > https://community.atlassian.com/t5/Jira-Core-questions/Project-based-labels-in-Jira/qaq-p/101203 > > > >>>> > > we > > > >>>> > > can disable labels field and create our own per-project custom > > > field > > > >>>> with > > > >>>> > > custom values defined. > > > >>>> > > > > > >>>> > > J. > > > >>>> > > > > > >>>> > > > > > >>>> > > On Fri, May 3, 2019 at 12:04 AM Aizhamal Nurmamat kyzy > > > >>>> > > <aizha...@google.com.invalid> wrote: > > > >>>> > > > > > >>>> > > > +1 on Ash's points. > > > >>>> > > > > > > >>>> > > > is it possible to disable labels to begin with? > > > >>>> > > > > I see no great benefit in having components with labels. > > > >>>> > > > > We can do just fine with only components. > > > >>>> > > > > > > > >>>> > > > I think we need to keep the labels for searchability and > > > >>>> findability: > > > >>>> > eg. > > > >>>> > > > user creates an issue with 'redshift' label within > > > 'aws-operators', > > > >>>> and > > > >>>> > > we > > > >>>> > > > want to allow everyone to look those issues up if they care > > only > > > >>>> about > > > >>>> > > > redshift. Also GSoC, GSoD, and other things that don't > > > necessarily > > > >>>> map > > > >>>> > to > > > >>>> > > > components. > > > >>>> > > > > > > >>>> > > > I also think that the "version" field should be mandatory. > > > >>>> > > > > It's important to know against which airflow version the > > > ticket is > > > >>>> > > > > reported. > > > >>>> > > > > > > > >>>> > > > +1 here. Users must know the version when they file a bug, > and > > > if > > > >>>> those > > > >>>> > > > bugs get fixed with newer versions, it would allow us to go > > > back and > > > >>>> > > close > > > >>>> > > > those issues more efficiently. Any other thoughts? > > > >>>> > > > > > > >>>> > > > Best, > > > >>>> > > > Aizhamal > > > >>>> > > > > > > >>>> > > > > > > >>>> > > > > > > >>>> > > > > > > >>>> > > > > > > > >>>> > > > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ > > > >>>> > > > > On Wednesday, May 1, 2019 12:17 PM, Ash Berlin-Taylor < > > > >>>> > a...@apache.org> > > > >>>> > > > > wrote: > > > >>>> > > > > > > > >>>> > > > > > This sounds like a fantastic idea. > > > >>>> > > > > > > > > >>>> > > > > > I would add to the list: > > > >>>> > > > > > > > > >>>> > > > > > - Remove labels that should be components (we have a > gcp > > > label > > > >>>> > and > > > >>>> > > a > > > >>>> > > > > gcp component for instance) - having duplication in them > is > > > >>>> confusing > > > >>>> > > > > > - Possibly use a label to indicate when an issue has > > > already > > > >>>> been > > > >>>> > > > > triaged (to avoid duplicated effort) > > > >>>> > > > > > > > > >>>> > > > > > We can delete components, but labels are Jira wide > so > > > apply > > > >>>> > > across > > > >>>> > > > > every ASF project so we can't do much about what appears > in > > > the > > > >>>> > > > > auto-complete. This would be the place where a Triager's > > Guide > > > >>>> would > > > >>>> > > come > > > >>>> > > > > in to play. > > > >>>> > > > > > > > > >>>> > > > > > -ash > > > >>>> > > > > > > > > >>>> > > > > > > > > >>>> > > > > > > On 1 May 2019, at 00:26, Aizhamal Nurmamat kyzy > > > >>>> > > > > aizha...@google.com.INVALID wrote: > > > >>>> > > > > > > Hello everyone, > > > >>>> > > > > > > I would like to propose a few changes for the Apache > > > Airflow > > > >>>> > JIRA. > > > >>>> > > > The > > > >>>> > > > > > > reason behind this proposal is that the set of > > components > > > is > > > >>>> > > > > disorganized, > > > >>>> > > > > > > and it could use some improvements to track the status > > of > > > the > > > >>>> > > project > > > >>>> > > > > and > > > >>>> > > > > > > improve the Jira triage. > > > >>>> > > > > > > I outlined all the proposed changes (and reasons > behind) > > > in > > > >>>> this > > > >>>> > > > > document > > > >>>> > > > > > > [1]. Please take a look and comment if you have any > > > >>>> suggestions. > > > >>>> > I > > > >>>> > > > also > > > >>>> > > > > > > created a public dashboard to to be able to look into > > some > > > >>>> > > statistics > > > >>>> > > > > > > around JIRA issues [2]. > > > >>>> > > > > > > The high level overview of changes is: > > > >>>> > > > > > > > > > >>>> > > > > > > - > > > >>>> > > > > > > > > > >>>> > > > > > > Clean up components that are typos, duplicates or > overly > > > >>>> specific > > > >>>> > > > > > > > > > >>>> > > > > > > > > > >>>> > > ------------------------------------------------------------------ > > > >>>> > > > > > > > > > >>>> > > > > > > Make component a required field when filing an issue > in > > > JIRA > > > >>>> > > > > > > > > > >>>> > > > > > > > > > ------------------------------------------------------------- > > > >>>> > > > > > > > > > >>>> > > > > > > Give a component to all issues that don’t have one at > > the > > > >>>> moment > > > >>>> > > > > > > > > > >>>> > > > > > > > > > >>>> ----------------------------------------------------------------- > > > >>>> > > > > > > > > > >>>> > > > > > > Ensure that no new components are created unless it’s > > > >>>> discussed > > > >>>> > by > > > >>>> > > > the > > > >>>> > > > > > > community > > > >>>> > > > > > > For further details, please take a look at the doc[1], > > and > > > >>>> share > > > >>>> > > your > > > >>>> > > > > > > thoughts on it. > > > >>>> > > > > > > Thank you, > > > >>>> > > > > > > Aizhamal > > > >>>> > > > > > > [1] > > > >>>> > > > > > > > > > >>>> > > > > > > > >>>> > > > > > > >>>> > > > > > >>>> > > > > >>>> > > > > > > https://docs.google.com/document/d/1gticSJ7LgD15XHgQhEP78-Ky38Er_NnMlarIvSQ8NYM/edit?usp=sharing > > > >>>> > > > > > > [2] > > > >>>> > > > > > > > > > >>>> > > > > > > > >>>> > > > > > > >>>> > > > > > >>>> > > > > >>>> > > > > > > https://issues.apache.org/jira/secure/Dashboard.jspa?selectPageId=12333933 > > > >>>> > > > > > > > >>>> > > > > > > > >>>> > > > > > > > >>>> > > > > > > >>>> > > > > > >>>> > > > > > >>>> > > -- > > > >>>> > > > > > >>>> > > Jarek Potiuk > > > >>>> > > Polidea <https://www.polidea.com/> | Principal Software > > Engineer > > > >>>> > > > > > >>>> > > M: +48 660 796 129 <+48660796129> > > > >>>> > > E: jarek.pot...@polidea.com > > > >>>> > > > > > >>>> > > > > >>>> > > > >>> > > > > > -- > > Jarek Potiuk > Polidea <https://www.polidea.com/> | Principal Software Engineer > > M: +48 660 796 129 <+48660796129> > E: jarek.pot...@polidea.com >
