Open
Bug 1509332
Opened 7 years ago
Updated 5 years ago
Stop hardcoding users, products, components, keywords, version in bug history; use IDs instead
Categories
(bugzilla.mozilla.org :: General, task, P2)
Tracking
()
NEW
People
(Reporter: marco, Unassigned)
References
(Blocks 1 open bug)
Details
This makes it hard to link the history results with the current results, where we only have the current email of the user.
Comment 1•7 years ago
|
||
Hmm, this is a bit difficult issue. In the history (bugs_activity) table, all the added/removed values are hardcoded as a comma-separated string. The solution may be storing unchangeable user IDs instead of email addresses, but we have to dig older emails in the audit log.
Comment 2•7 years ago
|
||
Emma also noticed this, which is actually not specific to the API.
Component: API → General
Comment 3•6 years ago
|
||
(In reply to Kohei Yoshino [:kohei] (Bugzilla UX) (FxSiteCompat) from comment #1)
Hmm, this is a bit difficult issue. In the history (bugs_activity) table,
all the added/removed values are hardcoded as a comma-separated string. The
solution may be storing unchangeable user IDs instead of email addresses,
but we have to dig older emails in the audit log.
Let’s do this.
Assignee: nobody → kohei.yoshino
Status: NEW → ASSIGNED
Priority: -- → P2
This is also an issue that can affect people whose email changes are associated with gender, relationship and other personal history matters.
Also, a reason to move off of email as a unique identifier.
Updated•6 years ago
|
Summary: History contains emails of users at the time when the changes were made → Stop hardcoding users, products, components, keywords in bug history; use IDs instead
Updated•6 years ago
|
Summary: Stop hardcoding users, products, components, keywords in bug history; use IDs instead → Stop hardcoding users, products, components, keywords, version in bug history; use IDs instead
Updated•6 years ago
|
Type: enhancement → task
Updated•6 years ago
|
Assignee: kohei.yoshino → nobody
Status: ASSIGNED → NEW
You need to log in
before you can comment on or make changes to this bug.
Description
•