We have 1k bugs. Would you like to help triage?

S by sjb007 on 17 Apr 2025 #

Does it take a while for the permissions to be provisioned in github? No change to the UI in the right side-bar so far.

M by Moult on 17 Apr 2025 #

I've sent an invite but you probably need to accept it. Check your inbox?

M by Moult on 17 Apr 2025, edited 17 Apr 2025 # +1 votes

BTW this is the equivalent of "needs triage" for Bonsai if you want a TODO list ;) is:issue state:open -label:Severity:Major -label:Severity:Minor -label:Severity:Critical label:Bonsai

S by sjb007 on 17 Apr 2025 #

Doh! I didn't realise it was so... consensual. Thought you'd just flip a switch and it'd be there. All good now.

F by falken10vdl on 17 Apr 2025 #

I have seen that there are +600 issues without a type value but only +20 issues without label.

Do we assign type to those 600? Does it make sense that type if not assigned it is assumed to be a bug?

What is the expected proccess?

Assign type -> assign label of product (bonsai, ifcopenshell, etc) ->...

Thanks!

T by theoryshaw on 17 Apr 2025 #

@Moult said:

BTW this is the equivalent of "needs triage" for Bonsai if you want a TODO list ;) is:issue state:open -label:Severity:Major -label:Severity:Minor -label:Severity:Critical label:Bonsai

would add...

is:issue state:open -label:Severity:Major -label:Severity:Minor -label:Severity:Critical label:Bonsai -type:Feature

S by sjb007 on 17 Apr 2025, edited 17 Apr 2025 #

And I would raise you...

is:issue state:open -label:Severity:Major -label:Severity:Minor -label:Severity:Critical label:Bonsai -type:Feature -type:Task

Am I missing something? Does Github not have a simple way to save my filters so I can switch between easily? (Not talking about saving the URL)

S by sjb007 on 17 Apr 2025, edited 17 Apr 2025 # +1 votes

OK, I deleted this, because a lot of that previous comment was dumb. This new filter is a doozy...

is:issue state:open -label:"Severity:Major","Severity:Minor","Severity:Critical" -type:"Feature","Task" -label:"IfcOpenShell-Python","IfcOpenShell-Core","IfcConvert","Ifc5D","IfcTester","IfcCSV","BCF","IfcPatch","IfcClash","IfcFM","IfcSverchok","IfcCityJSON","Ifc4D","bSDD","IfcMax","BIMTester"

M by Moult on 19 Apr 2025 #

Ive been noticing some inconsistencies in bug severity. Are there ambiguities to the definitions? Should the definitions be changed? Is it just me?

T by theoryshaw on 19 Apr 2025 #

I have a feeling there might always be a little bit of interpretation and bias, as well as lack of knowledge of the context, when choosing the 'correct' severity. Would think, however, that the triage team can self-correct itself through other's resetting the severity to a level that makes more sense to them.

S by sjb007 on 19 Apr 2025 # +1 votes

I'm trying to follow the description shown against the label. This is never a precise thing. I don't know if I'm the culprit, but I have done quite a bit of triage over the last day or so, although only a modest amount of level setting. I have a thick skin though, so if I'm getting it wrong just point out where and I'll adjust accordingly. My 4 step process is:

Not labelled with a component:

is:issue state:open -label:IfcOpenShell-Python,IfcOpenShell-Core,IfcConvert,Ifc5D,IfcTester,IfcCSV,BCF,IfcPatch,IfcClash,IfcFM,IfcSverchok,IfcCityJSON,Ifc4D,bSDD,IfcMax,BIMTester,Bonsai

Bonsai, Not typed:

is:issue state:open label:Bonsai -type:Bug,Feature,Task

Bonsai Bug, Not given severity:

is:issue state:open label:Bonsai type:Bug -label:Severity:Major,Severity:Minor,Severity:Critical

Confirmation still current in latest dev release.

1 is completed, but there are 4 left I'm not really sure of - I leave those for someone else to decide.

2 is in progress, 160 left to go.

3 to do, is currently at 27, but some portion of the 160 will be added to this number once typed.

to do - this will be the biggest grind.

S by sjb007 on 19 Apr 2025 #

Perhaps we can add another type of "Question". Sometimes I see things that are not Feature, Bug or Task, like https://github.com/IfcOpenShell/IfcOpenShell/issues/5627

(I assume there's no way to convert an issue into a Discussion item?)

M by Moult on 19 Apr 2025 # +3 votes

Cool all good, there's no right or wrong since labels are arbitrary, it's purely about consistency.

Feel free to close questions, they don't belong there. You can refer them to discussions or the OSArch forums. We now have a link when creating issues to help discourage them being posted as issues. Alternatively on the bottom right there is a "Convert to Discussion" link.

F by falken10vdl on 19 Apr 2025 #

So this means that the priority is to > @sjb007 said:

I'm trying to follow the description shown against the label. This is never a precise thing. I don't know if I'm the culprit, but I have done quite a bit of triage over the last day or so, although only a modest amount of level setting. I have a thick skin though, so if I'm getting it wrong just point out where and I'll adjust accordingly. My 4 step process is:

Not labelled with a component:

is:issue state:open -label:IfcOpenShell-Python,IfcOpenShell-Core,IfcConvert,Ifc5D,IfcTester,IfcCSV,BCF,IfcPatch,IfcClash,IfcFM,IfcSverchok,IfcCityJSON,Ifc4D,bSDD,IfcMax,BIMTester,Bonsai

Bonsai, Not typed:

is:issue state:open label:Bonsai -type:Bug,Feature,Task

Bonsai Bug, Not given severity:

is:issue state:open label:Bonsai type:Bug -label:Severity:Major,Severity:Minor,Severity:Critical

Confirmation still current in latest dev release.

1 is completed, but there are 4 left I'm not really sure of - I leave those for someone else to decide.

2 is in progress, 160 left to go.

3 to do, is currently at 27, but some portion of the 160 will be added to this number once typed.

to do - this will be the biggest grind.

Lovely explanation. Thanks for the filters. I am.now following the procedure you have explained. Thanks!

@Moult same here, maybe I am also not properly assigning bug levels. Feedback from senior developers is greatly appreciated to improve moving forward.

Thanks!

S by sjb007 on 20 Apr 2025, edited 20 Apr 2025 # +3 votes

@Moult Well I hope I haven't made too much of a mess. I cracked on a bit. I noticed other people working on this too, so I'm not trying to steal all the glory ;-) but I just thought a quick update here:

Not labelled with a component: Done, currently 3 left - I'm not confident of making a choice.
Bonsai, Not typed: Done, currently 6 left - likewise for someone else to choose.
Bonsai Bug, Not given severity: To Do, currently 27 left.
Confirmation still current in latest dev release: To Do. I've done a few already as I worked through 1 and 2, but many to go.

I think I might have a bit of a rest though.

It would be really nice to have a label to tag those that we've confirmed are still an issue in the latest dev release - i.e. the TriageSprint1:Confirmed label I mentioned in the chat channel.

S by sjb007 on 20 Apr 2025 # +5 votes

So 1, 2, and 3 are all pretty much done - seems others have been busy. There are a small number of issues that are head-scratchers that no-one seems able to nail down.

Open issue count is down to 900 - Yay!

Bonsai Bugs = 185, Features = 278, and Tasks = 14

For myself, I don't feel able to triage the non-Bonsai issues, so there are another 423 non-Bonsai issues.

All that is left now is to grind through all the open Bonsai bugs, and confirm if they are still reproducible in latest Bonsai.

M by Moult on 21 Apr 2025 # +8 votes

A huge thank you to everybody! It's been a huge help and we'll try our very best to resolve bugs as fast as we can!

Go to page: