Closed Bug 972040 Opened 7 years ago Closed 6 years ago

For bugs filed against Trunk, automatically set 'affected' release-tracking flags

Categories

(bugzilla.mozilla.org :: General, enhancement)

Production
enhancement
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: jruderman, Assigned: glob)

References

Details

Attachments

(1 file)

Al Billings says he spends lots of time setting release-tracking flags for trunk bugs. This seems silly because Bugzilla could do it automatically:

A) When a trunk bug is filed, set current version as 'affected'
       OR 
B) When a merge occurs, set the old trunk version as 'affected'

(I'm not sure which corresponds more closely with how the flags are used)
We run into the issue a lot where bugs are filed off of "mozilla central" but then triagers like me need to mark whatever version status flag corresponds to central as "affected" for tracking purposes. This becomes very tedious as a hand done process. It would be good if we could set this automatically in some fashion to remove the manual component.
i'd like to get confirmation of the details of your request.
is the following what you mean?

on the non-guided enter_bug page:

  if the status-firefox* tracking flags are applicable to the current product
     and the selected version is ("trunk" or the highest numbered status-firefox* field)
     and the status is not UNCONFIRMED
  then
    set the value of the highest numbered status-firefox* field to "affected"
    ensure the "set bug flags" div is expanded
Flags: needinfo?(abillings)
That is a solution that would work.
Flags: needinfo?(abillings)
I'm not thrilled about the "Expand the 'set bug flags'" part. It would pretty much always be expanded, making the page much longer and messier.

Why would someone file a bug against trunk and NOT want the trunk version set to affected?
Poking this a year later.
Flags: needinfo?(glob)
sorry, this request was lost in the pile'o'work.
Assignee: nobody → glob
Flags: needinfo?(glob)
Attached patch 972040_1.patch β€” β€” Splinter Review
- moves building of component --> visible flag from template to perl
- migrate from yui to jquery
- implement comment 2 minus auto expanding of the 'set bug fields' div
Attachment #8578678 - Flags: review?(dylan)
Comment on attachment 8578678 [details] [diff] [review]
972040_1.patch

Review of attachment 8578678 [details] [diff] [review]:
-----------------------------------------------------------------

r=dylan

confirmed that it does what it says on the tin. It's also > 100ms faster.
Attachment #8578678 - Flags: review?(dylan) → review+
To ssh://gitolite3@git.mozilla.org/webtools/bmo/bugzilla.git
   f45322b..3e7f7dd  master -> master
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Summary: For bugs filed against Trunk, automatically set 'affected' and 'fixed' release-tracking flags → For bugs filed against Trunk, automatically set 'affected' release-tracking flags
Depends on: 1170179
Blocks: 1170179
No longer depends on: 1170179
You need to log in before you can comment on or make changes to this bug.