When do issues go to the 'New' colum in a particular dashboard sig ? about core

[goern]

'new' is used for all the good ideas that are just 'a one-liner', things that are unrefined or could be done, or nice to have... this is similar to 'stakeholder backlog' of https://github.com/orgs/open-services-group/projects/21

after refining the issue/card, it should move to (product) backlog, and adhere to certain quality criteria described in the T&C document.

@schwesig @codificat

[goern]

@VannTen does that answer your question?

[goern]

/sig user-experience
/priority critical-urgent
/triage accepted

[VannTen]

Yes. I intended to close the issue with #435, that's a leftover. Thanks ! /close

[sesheta]

@VannTen: Closing this issue.

In response to this:

Yes.
I intended to close the issue with #435, that's a leftover.
Thanks !

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[VannTen]

'new' is used for all the good ideas that are just 'a one-liner', things that are unrefined or could be done, or nice to have... this is similar to 'stakeholder backlog' of https://github.com/orgs/open-services-group/projects/21

So basically, every single opened issue should be put in a new column of one SIG, right ? Could we say this maps to the needs-triage label ?

after refining the issue/card, it should move to (product) backlog, and adhere to certain quality criteria described in the T&C document.

That part was clear.