Cannot seem to edit whiteboard tags, change product & components, etc. My previous Mozilla bugzilla account (firstname.lastname@example.org) had access to be able to change these sort of details, but since I created a new bugzilla account (email@example.com), it seems that I do not have the same permissions/access as I had previously. Also, I can't seem to find the instructions to setup alias names eg: ":cyee" available on irc at @cyee for any questions.
Assignee: user-accounts → nobody
Component: User Accounts → Administration
Product: Bugzilla → bugzilla.mozilla.org
QA Contact: default-qa
Version: unspecified → Production
Your phonebook entry still has firstname.lastname@example.org as your Bugzilla account name. https://phonebook.mozilla.org/#search/cyee You need to change it to the new address and then we can update your permissions. Since you are still with Mozilla, any reason why you cannot use the email@example.com address for your BMO work? dkl
Updated my bugmail on phonebook to firstname.lastname@example.org I could use the old email, but I had several bugs ongoing while working as a volunteer and this new/different role, so I figure it would just be better to keep with what I have now. If there was an easy way to migrate and merge the account I think that would be most ideal, but I don't care too much about the old bug I was subscribed to. Thanks!
(In reply to Casey Yee from comment #2) > Updated my bugmail on phonebook to email@example.com > > I could use the old email, but I had several bugs ongoing while working as a > volunteer and this new/different role, so I figure it would just be better > to keep with what I have now. > > If there was an easy way to migrate and merge the account I think that would > be most ideal, but I don't care too much about the old bug I was subscribed > to. > > Thanks! Permissions updated for firstname.lastname@example.org. We can definitely merge email@example.com into firstname.lastname@example.org if you like? Want us to do that now? dkl
Sure let's do that. Thanks David!
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.