#8733 Help with default package assignee/CC
Closed: Fixed 4 years ago by catanzaro. Opened 4 years ago by catanzaro.

Describe what you would like us to do:

I just received this bug report.

Notice that when the bug was created, it was assigned to Eike and my old Bugzilla account, mcatanzaro+wrong-account-do-not-cc@posteo.net, was CCed. But I'm now the main admin of the package, so I would expect the bug would be assigned to me.

Further, I would expect my current Bugzilla account, @redhat.com, to be CCed. I've already updated FAS to use my Red Hat email. I've previously checked my Bugzilla settings on my old account and removed my component watching settings there, so the only reason I should be CCed is due to FAS. I suspect FAS is somehow permanently mapped to my old Bugzilla account or something like that, rather than updating to follow my email address?

(Having to use multiple Bugzilla accounts, and being unable to disable the old one, isn't great.)


When do you need this to be done by? (YYYY/MM/DD)

"Soonish" at your convenience, thanks! Arbitrary date: 2020/03/23


The problem is that "mcatanzaro@redhat.com" is not a valid bugzilla account. It seems your redhat account is truncated to 8 chars and perhaps the longer one is a email alias?

So, possible fixes:

  • Change your fas email to mcatanza@redhat.com

  • Bug RHIT to make your redhat account the full length. (I know this is possible as @dcantrell just went through that)

  • Create a new mcatanzaro@redhat.com bugzilla account (but this might not be possible since @redhat.com accounts are different. You likely cannot login to it except with password (no saml2)

Metadata Update from @kevin:
- Issue priority set to: Waiting on Reporter (was: Needs Review)

4 years ago

The problem is that "mcatanzaro@redhat.com" is not a valid bugzilla account.

Ah, sorry... my bad then, thanks for investigating. :(

I'll close this issue and reopen in the future if the problem doesn't go away after I fix FAS to use my truncated email. Being locked into using a stupid truncated email address is sad, but oh well.

Bug RHIT to make your redhat account the full length. (I know this is possible as @dcantrell just went through that)

@dcantrell, you succeeded at this? We were told during NHO this was not allowed, we could only create email aliases (which I believe are not usable on Red Hat Bugzilla).

Create a new mcatanzaro@redhat.com bugzilla account (but this might not be possible since @redhat.com accounts are different. You likely cannot login to it except with password (no saml2)

I think I tried to do that first, but RH Bugzilla wouldn't let me. Anyway, RH Bugzilla does not allow employees to change their email address.

Is saml2 the Red Hat Associate login link? I just checked now in Firefox and I see that it works there. I thought it was busted because in WebKit this link only refreshes the page without preforming a login. I wonder why. Anyway, I don't care; if it doesn't work in WebKit, I can't use it. I already can only log in with a password, and I have to log in again every time I restart my browser, because, since the upgrade to Bugzilla 5, Red Hat Bugzilla uses a session cookie for the login cookie instead of a permanent cookie, which is incredibly annoying and serves zero security benefit since my password is saved in gnome-keyring anyway. That's a Red Hat downstream customization; upstream Bugzilla does not do that.

Metadata Update from @catanzaro:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

@dcantrell, you succeeded at this? We were told during NHO this was not allowed, we could only create email aliases (which I believe are not usable on Red Hat Bugzilla).

NHO lied to you. It is possible, but it took a very long time for IT to implement. When it was first announced they asked for people to sign up who wanted to fix their username. It was then 1000 days later that IT contacted me to do the change (I am not making up that number...it was exactly 1000 days later).

The order of operations is key. Do internal RH changes first. And yes, your BZ account has nothing to do with your RH account. You have to change that yourself. Once the RH internal side is done, change the FAS side. That will involve creating a new account rather than changing your existing one, but the process is easy.

Was there a technical problem that required you to create a new FAS account? Updating email address in FAS is simple?

My FAS account name was 'dcantrel' to match my old RH account name. RH changed my account name to 'dcantrell' so I wanted to do the same with FAS. It was not just changing my email address on my FAS account.

Log in to comment on this ticket.

Metadata