#7028 New Repo for "rpms/python-prometheus_client"
Closed: Processed 6 years ago Opened 6 years ago by jcline.

{
 "bug_id": 1590452, 
 "repo": "python-prometheus_client", 
 "exception": false, 
 "description": "", 
 "branch": "master", 
 "action": "new_repo", 
 "upstreamurl": "", 
 "summary": "The Python client for Prometheus", 
 "namespace": "rpms", 
 "monitor": "monitoring-with-scratch"
}

The Bugzilla review bug creator could not be found in FAS. Make sure your FAS email address is the same as in Bugzilla.

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

6 years ago

Hi,

I accidentally opened it with the wrong bugzilla account, do I need to open a new bug using my jeremy@jcline.org bugzilla account?

No, reassigning it to that account should work.

As in reassigning the bug to the proper account? I assumed the bug creator email needs to match the FAS email and I don't think I can change the creator of the bug. I've assigned it to my the BZ account associated with this FAS account in case that does it.

Indeed, you can't change the creator of the bug. I'm guessing this is one of those things that this tool checks which it probably shouldn't. It's discouraged, but the original submitter dropping a package review and someone else taking it over does happen even though it shouldn't. Or sometimes people have more than one bugzilla account.

The current situation certainly is confusing, though. The same person submitted the ticket originally and is the bug assignee. It should be assigned to the person who did the review.

Fix the assignee and I can hack the tool to process the request.

Okay, I reset the assignee

Metadata Update from @tibbs:
- Issue status updated to: Open (was: Closed)

6 years ago

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

6 years ago

Log in to comment on this ticket.

Metadata