Bug details: https://bugzilla.redhat.com/show_bug.cgi?id=2079198 Information from BlockerBugs App: <img alt="2079198" src="https://qa.fedoraproject.org/blockerbugs/api/v0/bugimg/2079198" />
Commented but haven't voted yet: kparal
The votes have been last counted at 2022-04-28 16:04 UTC and the last processed comment was #comment-794852
To learn how to vote, see: https://pagure.io/fedora-qa/blocker-review A quick example: BetaBlocker +1 (where the tracker name is one of BetaBlocker/FinalBlocker/BetaFE/FinalFE/0Day/PreviousRelease and the vote is one of +1/0/-1)
BetaBlocker +1
BetaBlocker
FinalBlocker
BetaFE
FinalFE
0Day
PreviousRelease
+1
0
-1
FinalBlocker -1
The basic functionality works, just with an annoying (and temporary?) side effect in some cases.
I'd probably also vote -1 for the comment 0 description. But merging contacts just because you mistyped an email address (are they using email as a primary ID or what?) and then randomly switch contact names feels worse, see comment 3. I can file it separately, if you want to vote on it separately, though.
You can always delete the duplicated contact which is like an empty box. The original contact gets correctly updated. At least when I tried. If others do not find it that bad, I can also live with
Contrary opinion: I'm inclined to say this is basic functionality failure. At least it's pretty embarrassing. Sadly, it's not a new issue: I've know about this for a long time.
FinalBlocker +1
(In the off chance this somehow gets accepted despite all the -1 votes, we can also consider the late blocker rule to release anyway.)
Sorry to ask but ... if you have known about this problem and you think it is "basic functionality", why didn't you propose it then?
Hm, although it is a basic functionality failure in a core app, I suppose I probably am not regularly thinking about Fedora release blocker process when trying to edit contacts....
Metadata Update from @blockerbot: - Issue status updated to: Closed (was: Open)
Release F36 is no longer tracked by BlockerBugs, closing this ticket.
Log in to comment on this ticket.