Re: Achievement unlocked: fully triaged

2022-12-09 Thread Moritz Mack
Great, I really like the new simplified flow! Thanks for that! On 08.12.22, 19:48, "Kenneth Knowles" wrote: Merged it. Please be on the lookout for bugs I have introduced, since they could result in issues slipping through the cracks. On Wed, Dec 7, 2022 at 3:  31 PM Kenneth Knowles wrote: OK

Re: Achievement unlocked: fully triaged

2022-12-08 Thread Kenneth Knowles
Merged it. Please be on the lookout for bugs I have introduced, since they could result in issues slipping through the cracks. On Wed, Dec 7, 2022 at 3:31 PM Kenneth Knowles wrote: > OK I did my best in https://github.com/apache/beam/pull/24585 > > Yet another thought I had: Do we really need

Re: Achievement unlocked: fully triaged

2022-12-07 Thread Kenneth Knowles
OK I did my best in https://github.com/apache/beam/pull/24585 Yet another thought I had: Do we really need multiple templates? Do people like the tags in the titles? After creation all these things are "just labels" so there's no particular reason we need to conceptualize issues as partitioned

Re: Achievement unlocked: fully triaged

2022-12-06 Thread Robert Burke
+1 to letting conjunctions form naturally. In the bikeshedding discusion: That would mean I'm biased to having the reduced label set to have reduced colours for the general category. Eg. SDK colour, Runner colour, beam resources colour, and IO being it's own special unique colour, and awaiting

Re: Achievement unlocked: fully triaged

2022-12-06 Thread Danny McCormick via dev
I like that idea (and the list) as well. On Tue, Dec 6, 2022 at 1:59 PM Kerry Donny-Clark wrote: > I really like the idea of multi-select and automatic "awaiting triage". > Kenn, I think the list you have looks good to me. > > On Tue, Dec 6, 2022 at 1:55 PM Kenneth Knowles wrote: > >> Noting

Re: Achievement unlocked: fully triaged

2022-12-06 Thread Kerry Donny-Clark via dev
I really like the idea of multi-select and automatic "awaiting triage". Kenn, I think the list you have looks good to me. On Tue, Dec 6, 2022 at 1:55 PM Kenneth Knowles wrote: > Noting that what you've listed are the options in the issue template, > which are then expanded to multiple labels.

Re: Achievement unlocked: fully triaged

2022-12-06 Thread Kenneth Knowles
Noting that what you've listed are the options in the issue template, which are then expanded to multiple labels. So focusing on the issue template, I like the general idea, but maybe we can simplify it even more: When a user is filing a bug, I think a good outcome is for it to get into the right

Re: Achievement unlocked: fully triaged

2022-12-06 Thread Danny McCormick via dev
> Is it possible to not have a default option? Sadly, no AFAIK. I agree this would help. We could try things like making the default " " and auto-closing issues that don't pick something other than the default, that's a pretty rough experience though and not worth it IMO. > I definitely think

Re: Achievement unlocked: fully triaged

2022-12-06 Thread Bjorn Pedersen via dev
As someone still newer to Beam, I can attest that the number of labels can be overwhelming. Is it possible to not have a default option? Even just getting people to interact with the dropdown might go a long way, especially if the labels were fewer and clearer. Bjorn On Mon, Dec 5, 2022 at 6:46

Re: Achievement unlocked: fully triaged

2022-12-05 Thread Kenneth Knowles
I definitely think reducing the label zoo could help. We have a lot of labels that are decompositions of what used to be Jira components. Kenn On Mon, Dec 5, 2022 at 12:17 PM Danny McCormick via dev wrote: > > Previously, we had automation that would automatically mark > self-assigned

Re: Achievement unlocked: fully triaged

2022-12-05 Thread Danny McCormick via dev
> Previously, we had automation that would automatically mark self-assigned self-reported issues as triaged. That is probably a third of issues or more. I believe that automation exists now[1], but it wasn't retroactively applied to old issues. > One issue is that a lot of triage work is getting

Re: Achievement unlocked: fully triaged

2022-12-05 Thread Robert Burke
I do a regular look at the go label myself. Partly because that's the best way to learn what to fix next. On Mon, Dec 5, 2022, 11:57 AM Kenneth Knowles wrote: > Previously, we had automation that would automatically mark self-assigned > self-reported issues as triaged. That is probably a third

Re: Achievement unlocked: fully triaged

2022-12-05 Thread Kenneth Knowles
Previously, we had automation that would automatically mark self-assigned self-reported issues as triaged. That is probably a third of issues or more. I'm not sure what else. I appreciate Valentyn keeping an eye on the Python label. One issue is that a lot of triage work is getting the labels

Re: Achievement unlocked: fully triaged

2022-12-05 Thread Kerry Donny-Clark via dev
This is a glorious achievement Kenn! To keep things clean going forward are there any improvements we can make in our issue creation flow? On Fri, Dec 2, 2022, 6:44 PM Kenneth Knowles wrote: > Hi all, > > I've finally done it! I've emptied the label "awaiting triage". Help me > keep it that

Achievement unlocked: fully triaged

2022-12-02 Thread Kenneth Knowles
Hi all, I've finally done it! I've emptied the label "awaiting triage". Help me keep it that way! This ensures that we actually at least *look* at each issue once, preferably soon after it is filed. The idea is that you make sure the priority and other labels are right, since users are not