Closed
Bug 1353225
Opened 8 years ago
Closed 7 years ago
Release revision pages have incorrect 'Neither whitelisted nor mapped to.' strings on each revision
Categories
(Release Engineering Graveyard :: Applications: Balrog (frontend), enhancement, P3)
Release Engineering Graveyard
Applications: Balrog (frontend)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: nthomas, Assigned: alvin.mutisya, Mentored)
References
Details
(Whiteboard: [lang=js][lang=html][ready][good first bug])
Attachments
(1 file)
208.41 KB,
image/png
|
Details |
The screenshot is for a release which *is* mapped to on the beta-cdntest channel, so the 'Neither whitelisted nor mapped' string is incorrect, and also repeated. Should we just remove that from history pages (eg /releases/Firefox-53.0b9-build1) and just leave it on the list of Releases (/releases) ?
Comment 1•8 years ago
|
||
(In reply to Nick Thomas [:nthomas] from comment #0)
> Created attachment 8854283 [details]
> Screenshot
>
> The screenshot is for a release which *is* mapped to on the beta-cdntest
> channel, so the 'Neither whitelisted nor mapped' string is incorrect, and
> also repeated. Should we just remove that from history pages (eg
> /releases/Firefox-53.0b9-build1) and just leave it on the list of Releases
> (/releases) ?
Yeah, I think removing it is the right way to go.
Priority: -- → P3
Whiteboard: [lang=js][lang=html][ready][good first bug]
Updated•8 years ago
|
Mentor: bhearsum
Comment 2•7 years ago
|
||
Commit pushed to master at https://github.com/mozilla/balrog
https://github.com/mozilla/balrog/commit/f41081d06395dc39512c2a34c4261b29e6264084
bug 1353225: Remove mapping strings from release history pages (#395). r=bhearsum
Comment 3•7 years ago
|
||
This is production, thank you Alvin!
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Product: Release Engineering → Release Engineering Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•