Closed Bug 1360192 Opened 8 years ago Closed 6 years ago

add a warning when a Rule's channel is changing

Categories

(Release Engineering Graveyard :: Applications: Balrog (frontend), enhancement, P3)

enhancement

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: bhearsum, Unassigned, Mentored)

Details

Attachments

(1 file)

Changing the channel of a Rule should be a pretty rare operation. Doing so can often have big or unexpected impacts. We should add some level of warning in the UI, perhaps with some information or a link to something that talks about the potential implications of doing so, and things to consider before making the change.
Mentor: bhearsum
Priority: P2 → P3
Whiteboard: [lang=js][lang=html] → [lang=js][lang=html][good first bug][ready]
I would like to work on this, but will need some more details for a clear understanding.
(In reply to akriti verma from comment #1) > I would like to work on this, but will need some more details for a clear > understanding. Sure! I think it's best if you're able to run the local development environment before working on this. Can you try the instructions at http://mozilla-balrog.readthedocs.io/en/latest/contribute.html? Once you're able to access http://localhost:8080/rules, you should be ready to go. The idea is that when somebody clicks "Update" or "Schedule an Update" on a Rule, and then tries to change the "channel" value, a warning should be shown. This could take the form of an extra element in the modal dialog that pops up, or perhaps an alert when they click "Save Changes", or maybe something else. Does that make sense?
Assignee: nobody → akriti.v10
Hi Ben ,i want to upload a patch , but when i am executing git commands the patch is getting uploaded on github. How can i upload it on Bugzilla?.
(In reply to akriti verma from comment #3) > Hi Ben ,i want to upload a patch , but when i am executing git commands the > patch is getting uploaded on github. How can i upload it on Bugzilla?. Creating a pull request on Github is the right thing to do, if you can. Please send it to https://github.com/mozilla/balrog. If you have trouble with that, let me know.
Hi Ben, Can you please tell me what implications should be mentioned in the warning message?
I'm a student from coventry university studying an opensource module, I would like to be assigned this as my first bug! Could you please point me in the right direction of how to start
Unassigning due to inactivity.
Assignee: akriti.v10 → nobody
Whiteboard: [lang=js][lang=html][good first bug][ready]

Mass closure of old Balrog UI bugs. We've built a new UI in https://github.com/mozilla-frontend-infra/balrog-ui, and any issues which are still valid should be filed as Issues there.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
Product: Release Engineering → Release Engineering Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: