On Wed, 2023-08-23 at 09:28 -0400, Josh Boyer wrote:
On Wed, Aug 23, 2023 at 8:46 AM Neal Gompa ngompa13@gmail.com wrote:
On Wed, Aug 23, 2023 at 6:51 AM Florian Weimer fweimer@redhat.com wrote:
The Red Hat Platform Tools team (who maintain binutils, GCC, gdb, glibc, systemtap, valgrind, etc.) have begun to move bugs from bugzilla.redhat.com to issues.redhat.com, to the project called “RHEL”.
We'd appreciate if future issues discovered in CentOS Stream were filed there directly. When filing new issues, please make sure that the Security Level is set to None, so that others can contribute, and select “CentOS Stream” under Projects. Please do not use the public “CS” project for reporting issues in specific RPM packages because we (Platform Tools) do not monitor it. (Compose issues and CentOS Stream issues should still be reported in “CS”.)
The Red Hat Jira CS project currently blocks community members from filing issues or making comments.
Community members should be able to create a Red Hat account on sso.redhat.com and use that to login to issues.redhat.com. As far as I know, it's not necessary to agree to the Red Hat Enterprise Agreement, or any subscription terms. If that has changed, please let me know.
I don't know this personally, since my account is old and originates from the JBoss JIRA instance, but I've been told that you are required now to disclose address and phone number and agree to the RHEA TOS to access the Jira when you create your account. It would be worth double-checking this.
The user experience should remain largely unchanged, although the underlying technology is completely different (Jira vs Bugzilla). If a bug is migrated, a notification is posted to the Bugzilla bug, with instructions how to find the migrated issue on issues.redhat.com. You will likely have to re-subscribe to the new issue after migration. In the future, logging into issues.redhat.com from time to time (every few weeks or months) will be required to keep receiving notification for your bug subscriptions.
Please fix this and don't make accounts go automatically inactive. That's annoying and painful.
To my understanding, this will not be changed. Inactive accounts are culled to reduce seat license counts. I believe the cutoff is 90-days. While I agree it's a change in behavior and somewhat annoying, logging into the instance once a quarter does not seem onerous for someone that wants to actively participate.
josh
Will it send out a notification that an account is going to be disabled or do I need to add a calendar event to make sure I log in often enough?
Pat