Closed Bug 665717 Opened 14 years ago Closed 14 years ago

enable "needs-treeclosure" flag in all mozilla.org:ServerOps components

Categories

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

Product:
bugzilla.mozilla.org
Component:
Administration
Version:
Production
Platform:
x86
macOS
Type:
task
Priority:
Not set
Severity:
normal

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: joduinn, Assigned: glob)

Details

Some (but not all) ServerOps components have the "needs-treeclosure" ?/+/- flag, like is also in ReleaseEngineering component. Per email with mrz, this "needs-treeclosure" flag should be enabled for all ServerOps components, now that RelEng BuildDuty are coordinating tree-closures.
Assignee: nobody → glob
needs-treeclosure is now enabled on: Testing:General Testing:Infrastructure Testing:Mozmill Testing:New Frameworks Testing:Talos mozilla.org:MozillaBuild mozilla.org:Release Engineering mozilla.org:Release Engineering: Custom Builds mozilla.org:Server Operations mozilla.org:Server Operations: Account Requests mozilla.org:Server Operations: Database mozilla.org:Server Operations: Desktop Issues mozilla.org:Server Operations: Labs mozilla.org:Server Operations: Netops mozilla.org:Server Operations: Projects mozilla.org:Server Operations: RelEng mozilla.org:Server Operations: Security mozilla.org:Server Operations: Web Content Push
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Can you verify if this is correctly set for "mozilla.org:Server Operations: Netops"? I ask because I cannot see this flag for bug#662071, which needs a treeclosure. Further, I attempted to create a new bug in each of the 10 ServerOps components, but was only able to see+edit the needs-treeclosure flag in only 3 of the 10 components. Can you investigate?
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
sorry about that john, the flag's visibility should now be correct. note to self: don't forget to hit 'save changes'.
Status: REOPENED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → FIXED
(In reply to comment #3) > sorry about that john, the flag's visibility should now be correct. > > note to self: don't forget to hit 'save changes'. Thanks Byron. Looks like "save changes" did the trick, the flag works fine in all components!
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.