Closed Bug 1136979 Opened 9 years ago Closed 9 years ago

Minor Brand Initiation Form Updates

Categories

(bugzilla.mozilla.org :: Custom Bug Entry Forms, defect)

Product:
bugzilla.mozilla.org
Component:
Custom Bug Entry Forms
Version:
Production
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: jbalaco, Assigned: dkl)

Details

Hi, 

I need to make three (hopefully) minor updates to the Brand Initiation Form (https://bugzilla.mozilla.org/form.creative) 

1. Remove Creative Due Date option

2. Update language for the Launch date
Current:
Launch Date
When will your project go forth into the world? 

New:
Expected Launch Date
When do you anticipate your project launching? We will determine a creative due date with you based on this to ensure that it works for everyone.

3. Update auto-cc list:
Remove: enoonan@mozilla.com, gjost@mozilla.com, kbaird@mozilla.com

Let me know if you have any questions. Thanks!
Assignee: nobody → dkl
Status: NEW → ASSIGNED
Component: General → Custom Bug Entry Forms
OS: Mac OS X → All
Hardware: x86 → All
I have pushed the changes to our test server for your feedback. The CC list changes have already been done on production and didn't require code change.

https://bugzilla-dev.allizom.org/form.creative

Question: The old Creative Due Date field was removed which used the standard Due Date field in Bugzilla. Did you want me to put the value for Launch Date in the Due Date field instead or leave it in the text of the initial comment as it is now?

dkl
Flags: needinfo?(jbalaco)
Thanks, David!

The Due Date field can be left empty - I'll fill it in manually when we've determined the actual date. One last change - can you make the launch date a required field? 

Then this should be good to go. Thanks again!
Flags: needinfo?(jbalaco)
Committed. Will be in next weeks push to production.

To ssh://gitolite3@git.mozilla.org/webtools/bmo/bugzilla.git
   57ac7e0..a428a86  master -> master

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