You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 14, 2021. It is now read-only.
Not sure if this is the right place, but anyway ... I used to be maintainer of rubygem-linode [1], but I recently orphaned that package. However, the newly created bug by the-new-hotness [2] was assigned to me. Is this bug in PkgDb, new-hotness, bugzilla?
Actually I tried the "Reset Assignee to default for component" but it does not appear to change anything, so I suppose the PkgDb does not inform Bugzilla about the change of ownership correctly, since the new owner should be "orphan owner" user?
The text was updated successfully, but these errors were encountered:
Not sure if this is the right place, but anyway ... I used to be maintainer of rubygem-linode [1], but I recently orphaned that package. However, the newly created bug by the-new-hotness [2] was assigned to me. Is this bug in PkgDb, new-hotness, bugzilla?
Actually I tried the "Reset Assignee to default for component" but it does not appear to change anything, so I suppose the PkgDb does not inform Bugzilla about the change of ownership correctly, since the new owner should be "orphan owner" user?
The text was updated successfully, but these errors were encountered: