Closed Bug 1523620 Opened 6 years ago Closed 6 years ago

Add a Fission Tracking Flag

Categories

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

Staging

Tracking

()

RESOLVED FIXED

People

(Reporter: nika, Assigned: emceeaich)

References

(Blocks 1 open bug)

Details

It would be nice to have a milestone-based tracking flag for Fission, with an option to request Fission triage. It would be good to start with 3 milestones.

  • M1 (current)
  • M2 (next)
  • M3 (future)

As we complete milestones, we can add new milestones and re-triage items from Milestone 3 into them.

Flags: needinfo?(ehumphries)

Which products other than Core should Fission apply to?

Flags: needinfo?(ehumphries) → needinfo?(nika)

Nika, I've created Fission Milestone (cf_fission_milestone) as a "project" tracking flag with the values:

  • ---
  • ?
  • M1
  • M2
  • M3

And added the flag to all the firefox-related components (we can restrict that list later).

If the milestones M1 to M3 relate to releases, you may want to consider a query which would check to see if triage priorities are consistent with the milestone, i.e:

  • If priority = P1 then Fission Milestone = M1?
  • If priority = P2 then Fission Milestone = M2?
  • If priority = P3 then Fission Milestone = M3?

If that's not how the flag aligns with Priority, would the Iteration field, which some teams use to schedule work in advance, be useful here?

Assignee: nobody → ehumphries
Status: NEW → ASSIGNED
Priority: -- → P1

Thanks Emma. Could you please add a 'future' value also for the cf_fission_milestone flag so we can keep all the ones not in any one of the triaged milestones in that bucket?

(In reply to Neha Kochar [:neha] from comment #3)

Thanks Emma. Could you please add a 'future' value also for the cf_fission_milestone flag so we can keep all the ones not in any one of the triaged milestones in that bucket?

Done!

(In reply to Emma Humphries, Bugmaster β˜•οΈπŸŽΈπŸ§žβ€β™€οΈβœ¨ (she/her) [:emceeaich] (UTC-8) needinfo? me from comment #4)

(In reply to Neha Kochar [:neha] from comment #3)

Thanks Emma. Could you please add a 'future' value also for the cf_fission_milestone flag so we can keep all the ones not in any one of the triaged milestones in that bucket?

Done!

Thanks much, Emma! :)

Emma, is it possible to make only the ? option available for everyone, and restrict the m* and future settings for only certain folks who should be responsible for triaging the Fission bugs? That would include Nika and me for now. And if you can give us permissions for editing that list, we can make changes to it, as needed.

This is really awesome :-) -- thanks so much Emma!

Flags: needinfo?(nika)

(In reply to Neha Kochar [:neha] from comment #6)

Emma, is it possible to make only the ? option available for everyone, and restrict the m* and future settings for only certain folks who should be responsible for triaging the Fission bugs? That would include Nika and me for now. And if you can give us permissions for editing that list, we can make changes to it, as needed.

This is possible, and pretty common with how tracking flags are used.

Flags: needinfo?(ehumphries)

I'll make a group with :nika and :neha to manage that: mozilla-fission-drivers and mozilla-fission-drivers-team.

Flags: needinfo?(ehumphries)

I've made that a group. Neha, you can add people to mozilla-fission-drivers-team from https://bugzilla.mozilla.org/editusers.cgi.

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

Emma, thanks much for the help. I don't seem to have permissions for editusers. How can I request that?

Flags: needinfo?(ehumphries)
Blocks: 1549430
No longer depends on: 1549430
You need to log in before you can comment on or make changes to this bug.