Closed Bug 826296 Opened 11 years ago Closed 11 years ago

Changes to Air Mozilla Event Request Form

Categories

(bugzilla.mozilla.org :: User Interface, defect)

Production
x86
All
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: richard, Assigned: dkl)

References

()

Details

1 - Add two lines of small type below the Start Time dropdowns:
       Summer:  MTV/SFO/PDX/YVR UTC-7  TOR/BOS UTC-4  LON UTC+1  PAR/BER UTC+2
       Winter:  MTV/SFO/PDX/YVR UTC-8  TOR/BOS UTC-3  LON UTC    PAR/BER UTC+1

2 - The results of the "Show on large screens..." checkboxes should appear in the bug comment.

3 - Change "This event may..." to "This event may be seen by:" and change the radio buttons to:
"the Public", "Vouched Mozillians and MoCo/MoFo Staff", "MoCo/MoFo Staff Only"

None of the radio buttons should be selected by default, but setting one is required to submit the form.
(Event requests with either Mozillians or Staff Only set should be marked MoCo confidential in bugzilla)

4 - Remove the "Air Mozilla Broadcasting" checkbox.

5 - Remove the "Need IT help..." checkbox.

6 - Text entered in the Special Requests text area should appear in the bug comment.
Assignee: nobody → dkl
Status: NEW → ASSIGNED
I have made the requested changes and installed them to our test instance for your approval

https://bugzilla-stage-tip.mozilla.org/form.brownbag

The changes should show up there shortly. If they look OK we can get them pushed to production early next week.

dkl
Flags: needinfo?(richard)
Three phantom fields appear in the bug comment:  Audience:  Dial-In: and Archive:.
These are not in the form but do generate output somehow.

See https://bugzilla-stage-tip.mozilla.org/show_bug.cgi?id=686766

...and one that was an unclear spec on my part:  The text "Event requests with either Mozillians or Staff Only set should be marked MoCo confidential in Bugzilla" was meant to be an indication of how the form should work, not a label.  

Can we make the generated bug MoCo confidential in those cases?
Flags: needinfo?(richard)
Thanks for the feedback

(In reply to Richard A Milewski[:richard] from comment #2)
> Three phantom fields appear in the bug comment:  Audience:  Dial-In: and
> Archive:.
> These are not in the form but do generate output somehow.
> 
> See https://bugzilla-stage-tip.mozilla.org/show_bug.cgi?id=686766

Fixed.
 
> ...and one that was an unclear spec on my part:  The text "Event requests
> with either Mozillians or Staff Only set should be marked MoCo confidential
> in Bugzilla" was meant to be an indication of how the form should work, not
> a label.  

I have reworded it back similar to how it was. The old wording needed changing anyway since it was no longer a Yes/No choice. Please let me know if it looks good now.
 
> Can we make the generated bug MoCo confidential in those cases?

Currently it is configured to add the group if anything other than "The Public" is selected.

dkl
Flags: needinfo?(richard)
David,

Sorry!  This one is completely my error.  I failed to catch that you're setting the PRflag.  This is no longer necessary since we've moved the PR approval process into the AirMozilla site itself.

Other than that it looks good.
Flags: needinfo?(richard)
Cool. Removed the flag code and committed the changes. Should be in next weeks code push.

Committing to: bzr+ssh://dlawrence%40mozilla.com@bzr.mozilla.org/bmo/4.0
modified extensions/BMO/template/en/default/bug/create/comment-brownbag.txt.tmpl
modified extensions/BMO/template/en/default/bug/create/create-brownbag.html.tmpl                                                                              
Committed revision 8428

Committing to: bzr+ssh://dlawrence%40mozilla.com@bzr.mozilla.org/bmo/4.2
modified extensions/BMO/template/en/default/bug/create/comment-brownbag.txt.tmpl
modified extensions/BMO/template/en/default/bug/create/create-brownbag.html.tmpl                                                                              
Committed revision 8476

dkl
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.