Closed Bug 1553597 Opened 6 years ago Closed 5 years ago

Enable MOVED resolution for Web Compatibility product

Categories

(bugzilla.mozilla.org :: Administration, task, P3)

Product:
bugzilla.mozilla.org
Component:
Administration
Version:
Production
Type:
task

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: miketaylr, Assigned: emceeaich)

References

Details

It should require a See Also field to point to the new location (a webcompat.com/* or github.com/webcompat/web-bugs/* URL).

The use case is we'd like to move all webcompat bugs to our GitHub web-bugs project for investigation, to keep all our eggs in the same basket.

We'd have to enable it for all bugs, which isn't a terrible idea, but we'd need to advise people and write some Auto Nag rules to ensure this is being used correctly.

The two autonag rules that come to mind are:

  1. Web Compatibility bugs resolved as MOVED must have a See Also field value matching webcompat.com/* or github.com/webcompat/web-bugs/*.
  2. All other bugs resolved as MOVED must have a non-empty See Also field.

The next steps would be to get agreement that we can make this change, then setup the rules, then enable the new value.

Assignee: nobody → ehumphries
Priority: -- → P3
Version: Staging → Production

(In reply to Emma Humphries, Bugmaster ☕️🎸🧞‍♀️✨ (she/her) [:emceeaich] (UTC-8) needinfo? me from comment #1)

The next steps would be to get agreement that we can make this change, then setup the rules, then enable the new value.

SGTM!

See Also: → 1573155

For now the rules will be:

  1. Bugs in Core, Firefox, and Toolkit should not have a resolution of MOVED
  2. Web Compatibility bugs resolved as MOVED must have a See Also field value matching webcompat.com/* or github.com/webcompat/web-bugs/*
  3. All other bugs resolved as MOVED must have a non-empty See Also field

This has been turned on in production Mozilla and there's an automated whine report to monitor resolutions.

Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED

Awesome, thanks! I'll start playing with it and we'll develop some tooling to make it nice (like a web extension or something).

You need to log in before you can comment on or make changes to this bug.