Bug 1657507

Summary: Unable to set component and voter email preferences
Product: [Community] Bugzilla Reporter: Alasdair Kergon <agk>
Component: User AccountsAssignee: Jeff Fearn 🐞 <jfearn>
Status: CLOSED CURRENTRELEASE QA Contact: Rony Gong 🔥 <qgong>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 5.0CC: agk, jpichon, khong, liyu, qgong, thoger
Target Milestone: 5.0-RH2   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 5.0.4.rh13 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-02-13 02:13:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alasdair Kergon 2018-12-09 16:51:56 UTC 
At https://bugzilla.redhat.com/userprefs.cgi?tab=email

Choose 'Enable All Mail' then 'Submit Changes'

The changes to the component and voter column are lost.
Comment 1 Rony Gong 🔥 2018-12-10 07:35:04 UTC 
QE can reproduce this bug.
Comment 2 Tomas Hoger 2018-12-14 09:38:19 UTC 
Looking at the html source, this is likely related to the missing relationship id.  Each checkbox html element has a name as email-0-1, where first number is the relationship id (table columns) and the second is the event id (table lines).  Names for the Component and Voter columns lack relationship id, using element names of email--1.  Voter used to be 4, Component is a new thing.
Comment 3 Rony Gong 🔥 2018-12-19 06:05:34 UTC 
Verified on QA server
Comment 4 Jeff Fearn 🐞 2019-02-06 07:11:16 UTC 
This change has been deployed to partner Bugzilla [1] for pre-release testing, if your testing reveals any issues please update this bug.

1: https://partner-bugzilla.redhat.com/
Comment 5 Jeff Fearn 🐞 2019-02-13 02:13:32 UTC 
This change is now live. If there are any issues, do not reopen this bug.                                                                                                           
Instead, you should create a new bug and reference this bug.