Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bugzillas created by Reporter: [email protected] have Triaged keyword #312

Open
adelton opened this issue Nov 27, 2020 · 3 comments
Open

Comments

@adelton
Copy link

adelton commented Nov 27, 2020

Bugzillas created by The-new-hotness / [email protected] have Triaged keyword set. That does not seem correct. While I was not able to quickly find any rules for using Triaged in Fedora, the word suggests that someone took a look at the bug report and made some preliminary decision whether the bug is valid, whether component is correct, whether more info is needed, etc.

Having the Triaged keyword set directly by the reporter diminishes any value that the keyword might have. Please do not set it automatically.

@Zlopez
Copy link
Contributor

Zlopez commented Nov 30, 2020

I looked at the current configuration of the-new-hotness in our infra and we are creating the new ticket in bugzilla with the status 'NEW'. See https://pagure.io/fedora-infra/ansible/blob/master/f/roles/openshift-apps/the-new-hotness/templates/config.toml#_111

Not sure why the tickets are with the status Triaged instead.

@adelton
Copy link
Author

adelton commented Nov 30, 2020

@Zlopez
Copy link
Contributor

Zlopez commented Nov 30, 2020

Sorry, I was looking at the bug status not keywords. I'm not sure why this keyword is used, but for me the status would be the one I would look at.

My guess would be that the triaged keyword is used, because the upstream version was already released. But I wasn't here when this decision was made, so it's hard to say.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants