Open Jay-o-Way opened 2 years ago
Aaron-Junker
commented
2 years ago @crutkas answer from #16565:
I'm going to close this out as ultimately, this will be the plan but as of now, they are not in a state where we can. Chances are when terminal does, we will as well.
we'll revisit in a few months but right now, just some big deal breakers for speed of triage.
Jay-o-Way
commented
2 years ago Okay I see. But it is a few months later now. And I don't have any experience of working with Projects, so I don't know (yet) how that influences triage..
crutkas
commented
2 years ago Triages goal is to get clarity, see if we can reproduce the bug (if it is one), dedup and be sure we understand what is being asked.
Just because it is there now doesn’t mean we need to instantly use it. I’ll try it again soon
Jay-o-Way
commented
1 year ago 
Aaron-Junker
commented
1 year ago @Jay-o-Way you have to click on the repository tab to see the projects
Jay-o-Way
commented
1 year ago @Aaron-Junker you mean this one?
(I think) They're empty because the now "normal" Projects are not used.
Aaron-Junker
commented
1 year ago 
Weird. I have no problem with it
Jay-o-Way
commented
1 year ago Oh in that case it must be a matter of access/rights I guess
Aaron-Junker
commented
1 year ago Some concepts how it could be configured:
--
--
--
--
--
--
--
--
--
crutkas
commented
1 year ago I need to see how this works now vs before. The issue was linking stuff was tied to the organization aka Microsoft. Trying to quick assign stuff was … interesting
with that said, been a while. Right now this is not a pressing issue IMO unless I’m missing something
Jay-o-Way
commented
1 year ago @crutkas @jaimecbernardo @Aaron-Junker @htcfreek @niels9001 : Let me know if and how much you want me to take this up, I'm full of ideas 👍
Aaron-Junker
commented
1 year ago @crutkas @jaimecbernardo @Aaron-Junker @htcfreek @niels9001 : Let me know if and how much you want me to take this up, I'm full of ideas 👍
I would suggest adding about 10 issues to this repo that are just for testing purposes.
Jay-o-Way
commented
1 year ago I would suggest adding about 10 issues to this repo that are just for testing purposes.
idk, I'm confident enough to "show it by doing it" :)
Aaron-Junker
commented
1 year ago @jay-o-way I added some fields, when you want to experiment with them. I also added blocked as a status.
I thought in "external dependency" we could write why a certain item is blocked. The other fields should be self-explanetory.
Jay-o-Way
commented
1 year ago Getting curious what the other main colleagues think... @niels9001 @stefansjfw @SeraphimaZykova @davidegiacometti @jaimecbernardo @snickler @yuyoyuppe
Jay-o-Way
commented
1 year ago Fun fact: The (single-select) fields can now be colored and can have a description, just like labels! 😄
We should use the new version of "Projects". https://docs.github.com/issues/planning-and-tracking-with-projects/creating-projects/migrating-from-projects-classic
Also handy: https://github.com/orgs/github/projects/4247/views/1?filterQuery=-status%3A%22Q4+2021+%E2%80%93+Oct-Dec%22%2C%22Q1+2022+%E2%80%93+Jan-Mar%22+Projects
YouTube: https://youtu.be/MYNIXz9iViU (10 min.) https://youtu.be/UTDAlZFhPyM (4 short videos)
Personally, I would make one for each module. More specific: Large issues (read: projects) that are on the backseat but definitely need attention:
No projects for:
We currently have 121 labels (!) After using projects, we need a lot less labels, so we can clean them up!
Projects (products/toys) (~26 labels)
Fields (status/properties) (24~34 labels)
Resolution-xxx (10) doesn't need to be a field, because you can't apply a field if an issue is not linked to a project.
(I have many, many more ideas regarding labels, but that can be addressed in a different issue.)
Questions
Made a personal repo
https://github.com/Jay-o-Way/Learning-this
Have a look at my Discussions, Milestones and Projects!
Project:
Properties/fields when viewing an issue: