Closed Bug 864504 Opened 7 years ago Closed 7 years ago

Brand Engagement project initiation form that spits out a bug by default

Categories

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

Production
task
Not set

Tracking

()

RESOLVED FIXED

People

(Reporter: tshahian, Assigned: dkl)

References

Details

Attachments

(3 files)

Hi!  I'd like to create a project initiation form for the Brand Engagement team. This is part of a larger effort in optimizing our process and helping us manage the many requests and pings that we get.  The goal is to have a brief form that captures the basics of each request and spits out a bug (auto-populating the designated fields).  We would then triage and continue the conversation from there.  I'm not entirely sure how advanced these forms can be, but I have taken a look at two existing ones (below) and used those to spec out the one I would like to build.  If there are additional forms you can share for reference, or any other guiding tips, that would be great. 

I'm not entirely sure what the process is for doing this, or how long it takes, so if you can provide some guidance I would really appreciate it.  I'm still in the process of finalizing the form fields and desired behavior, but wanted to file the bug asap.

* https://bugzilla.mozilla.org/form.moz-project-review
* https://intranet.mozilla.org/webtools/webdev/project_init

What is the next step? Happy to set up a call to chat if that is best.  Thanks in advance for your help.
I also filed a bug to have the "due date" field available to the marketing component (specifically for design/copy).  Since that will be part of the initiation form, I'm going to add it as a dependency. Bug #864499
Depends on: 864499
No longer depends on: 864499
Depends on: 864499
Sure. We would be happy to help. Other sample forms are:

https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla+Reps&format=mozreps
https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla+Developer+Network&format=mdn
https://bugzilla.mozilla.org/enter_bug.cgi?product=Internet+Public+Policy&format=ipp

and a few others. 

We just need a list of fields and their descriptions. And possibly how they would map to real Bugzilla fields where possible. The rest could just be placed in the initial comment as formatted text.

dkl
Thanks David. Very helpful.  Few additional questions:

* How long does it take to set up a form once I've submitted the desired fields and behavior?

* Is it possible to make changes once it has been built? It's our first time doing this and I suspect we may need to test it a little and make adjustments to optimize as we go.  I don't anticipate lots of changes but want to make sure we have the ability to make some changes as needed.

* I just commented on the bug regarding Due Dates and if we can change the formatting on that, it appends a time stamp 00:00:00 right now which is unnecessary for us.  Let me know your thoughts on that please.

* what are our options with respect to he formatting / design of the form? I've noticed some variation between the existing forms and was curious to see if we had the ability to apply a tiny bit of design enhancement to this or if it's based on standard templates we can't touch.  

Thanks again.
Here is the current state of the form:

The copy can be found on this etherpad: 
https://etherpad.mozilla.org/CreativeInitiationForm

I've also attached a rough screenshot. Not intended for design purposes but just for reference.

I'm not entirely sure how things will behave once this form is submitted, but I'm assuming that each section is presented in Comment #0 of the bug, correct?  please let me know.

* Launch date is just for reference, but the "due date" should populate the due date field on bugzilla. Hopefully without the 00:00:00 time stamp...

* Im hoping we can use the calendar widgets for the dates.

* The "goals" section is a drop-down with the fields: 
-- Firefox Deskop
-- Firefox OS
-- Firefox Android
-- Firefox Marketplace
-- Corporate Support
-- All
-- Other

If possible, it would be good if "other" could be open field or trigger one so that we can understand what goal it serves if none of the above.

* Points of contact is basically who should be cc-ed on the bug, so... please cc the folks listed.

* when they hit "submit", do we get a "thank-you" confirmation page?  if so, I'd like to provide specific copy for this.  If not, I'll re-word the existing blurb surrounding the Submit button.  

* when submitted I would like the bug generated to be under the "marketing" product, and default to "design".  Automatically cc-ing myself, John, and Kristin.

I hope this helps.
Hi guys, I know I only posted a few days ago but wanted to just check and see if you had any questions and if you had a rough estimate of when you think this form could be done.  We've got a new process that we're looking to put in place and this form will really help us get going on that. Thanks again for your help.  Excited about this.
(In reply to Tara (musingt) from comment #4)
> Here is the current state of the form:
> 
> The copy can be found on this etherpad: 
> https://etherpad.mozilla.org/CreativeInitiationForm
> 
> I've also attached a rough screenshot. Not intended for design purposes but
> just for reference.
> 

I did not see the screenshot. Is it located somewhere else?

> I'm not entirely sure how things will behave once this form is submitted,
> but I'm assuming that each section is presented in Comment #0 of the bug,
> correct?  please let me know.

Yes. Anything that doesn't map to a specific Bugzilla field, will just go in the comment text.
 
> * Launch date is just for reference, but the "due date" should populate the
> due date field on bugzilla. Hopefully without the 00:00:00 time stamp...

That is part of another bug being worked on.

> * Im hoping we can use the calendar widgets for the dates.

Yes.
 
> * The "goals" section is a drop-down with the fields: 
> -- Firefox Deskop
> -- Firefox OS
> -- Firefox Android
> -- Firefox Marketplace
> -- Corporate Support
> -- All
> -- Other
> 
> If possible, it would be good if "other" could be open field or trigger one
> so that we can understand what goal it serves if none of the above.

We can make the "Other" value open up a free text field. We have done this with several other forms.
 
> * Points of contact is basically who should be cc-ed on the bug, so...
> please cc the folks listed.

Sure
 
> * when they hit "submit", do we get a "thank-you" confirmation page?  if so,
> I'd like to provide specific copy for this.  If not, I'll re-word the
> existing blurb surrounding the Submit button.  

The latter will be simpler as normally when a bug is created it just displays the new bug 
similar to how you see it if you were to visit the bug id at some later time.
We can display a custom confirmation page after submission but it adds a quite a bit of complexity to the task.

> * when submitted I would like the bug generated to be under the "marketing"
> product, and default to "design".  Automatically cc-ing myself, John, and
> Kristin.

No problem. We can add you to the default cc for the component.

I can try to take a look at this today. We normally push changes to production on Thursdays so optimistically it could go out this Thurs if all goes well, otherwise it will go out next Thursday. 

dkl
Assignee: nobody → dkl
Status: NEW → ASSIGNED
I have uploaded an initial version of this new form to our test instance for your feedback.

https://bugzilla-dev.allizom.org/enter_bug.cgi?product=Mozilla&format=creative

Still to do:
1. Need content for confirmation page once bug is submitted.
2. Update .htaccess to create shortcut for the form (i.e. https://bugzilla.mozilla.org/form.creative)

Give it a try

dkl
Flags: needinfo?(tshahian)
(In reply to David Lawrence [:dkl] from comment #7)
> I have uploaded an initial version of this new form to our test instance for
> your feedback.
> 
> https://bugzilla-dev.allizom.org/enter_bug.
> cgi?product=Mozilla&format=creative
> 
> Still to do:
> 1. Need content for confirmation page once bug is submitted.
> 2. Update .htaccess to create shortcut for the form (i.e.
> https://bugzilla.mozilla.org/form.creative)
> 
> Give it a try
> 
> dkl

Sorry, the correct URL is:

https://bugzilla-dev.allizom.org/enter_bug.cgi?product=Marketing&format=creative

dkl
Ping. We did not end up doing our normal Thurs push this week and will be possibly doing one on Monday instead. If you want this form to be live before next Thursdays push, please take a look at it today if you can.

Thanks
Thank you for the ping.  Sorry my computer crashed and I've been slower than anticipated in following up. 

Great to see a test up and running. Thanks again. 

I'm sorry I thought I had attached the screenshot but seems like it didn't go through and now I don't have the image since I'm on a loaner laptop.  

Few thoughts / questions:

* i did a test run and it seems like all the form fields did not make it through to the bug, see: bug #843813

* I would say launch date and creative due date are not required since they may not have that information or it may not relate.  lets remove them as required fields, unless it's possible to add a "TBD" type of option. If not, lets just make them optional.

* Is it possible to change the formatting of the form? and possibly the formatting of what is spit out into the bug?  

* wrt formatting the form, are there any design elements we can tweak/add (such as color / images, etc) ?

* I did not see a "thank you" or confirmation page, it went straight to the bug, which is great.  but I'd like to include the copy I had in the etherpad before the "submit" button, which was:

Thanks! Once you hit submit, your request will go off into the vortex of creative magic. What happens there is a closely guarded secret. We'd tell you, but honestly we don't know.
Flags: needinfo?(tshahian)
(In reply to Tara (musingt) from comment #10)

> 
> * i did a test run and it seems like all the form fields did not make it
> through to the bug, see: bug #843813

woops, seems like it doesn't file a real bug since it's a test installation of the form. attaching a screenshot to show you what I meant.
(In reply to Tara (musingt) from comment #10) 
> * i did a test run and it seems like all the form fields did not make it
> through to the bug, see: bug #843813

All values should be accounted for. Here is how they map:

Project / Request Title ==> Bug Summary (at the top of the bug report)

Project Overview ==> Added to the initial bug comment

Creative Specs and Deliverables ==> Added to the initial bug comment

Launch Date ===> Due Date field on the right column

Creative Due Date ==> Added to the initial bug comment

Mozilla Goal ==> Added to the initial comment

Point of Contact ==> Any values there are added to the cc list of the bug in the right column

Other bug values such as Product, Component, etc. are hard coded in the form itself.

Let me know if you want to change any of these.

> * I would say launch date and creative due date are not required since they
> may not have that information or it may not relate.  lets remove them as
> required fields, unless it's possible to add a "TBD" type of option. If not,
> lets just make them optional.

I have made them optional and pushed these changes to our test instance.

> * Is it possible to change the formatting of the form? and possibly the
> formatting of what is spit out into the bug?  

Sure. They are merely templates and we can add any customizations needed. To both the entry form and the comment text for the resulting bug. Just let us know how you want it to be formatted. We start out with basic forms and work up from there.
 
> * wrt formatting the form, are there any design elements we can tweak/add
> (such as color / images, etc) ?

Same as above.

> * I did not see a "thank you" or confirmation page, it went straight to the
> bug, which is great.  but I'd like to include the copy I had in the etherpad
> before the "submit" button, which was:

I have added the text above the submit button and pushed the change to our test instance.
 
dkl
Flags: needinfo?(tshahian)
Hi there. Sorry for the slow response.  The current version is a great start and very helpful to see it up on stage.  I'd love to make some changes though if you don't mind.  Here is what I would like to do (below) please let me know if there are any issues:

Looking at the formatting of this smartsheet form: 
https://www.smartsheet.com/b/publish?EQBCT=e3f63ab77acb4a719f9a43348956ecfb

* Please follow a similar formatting where the information is left justified and stacked on top of each other. 

* Please set a line-length limit so that the header/sub-head don't extend beyond the input field but wrap down. 

* Can you please change the background color of the form to this gradient: 
light blue/grey gradient (from light to dark / top to bottom)
#EAEFF2 to #D4DDE4

* The "*" Required asterisks - change color to #EA3B28

* I'm not sure if we can change the font, but if we can: Let's use Open Sans #282828

* I'm working with Lee to get a simple graphic for the header space.  Can you let me know if you need something other than a transparent PNG? I'll give that to you asap. It's just a little something to help bring the form to life. Nothing crazy.

* Can we change the button style/color? If so, would be great to grab the blue button from our style guide: http://www.mozilla.org/en-US/styleguide/websites/sandstone/buttons/ under "user flow" 

* Can we please edit the closing copy to this: 

" Thanks! Once you hit submit, your request will go off into the vortex of creative magic. (Actually, it goes to Bugzilla, but that doesn't sound as cool.) We'll be in touch soon with next steps and to let you know if we need any additional info. "

--------

Huge thanks again.  Please let me know if any of this is a concern.
Flags: needinfo?(tshahian)
I forgot to mention the padding: I'd like to follow a similar padding as what we saw in that smartsheet form.  Right now the text and input fields are a little jammed close together.  I think the smartsheet form is a good reference to follow for that as well. Please not that we don't need to insert the form fields into a new container like the smartsheet does.  Having the text and form fields set against a single background is fine.  Let me know if that sounds confusing.  Thanks again.
we have a mockup to help translate everything I just said into a visual reference :) I hope this helps  Lee will follow up with the PNG for that graphic, otherwise the rest of the mockup should mirror (more or less) the direction I just provided.
(In reply to Tara (musingt) from comment #14)
> * Can we change the button style/color? If so, would be great to grab the
> blue button from our style guide:
> http://www.mozilla.org/en-US/styleguide/websites/sandstone/buttons/ under
> "user flow" 

we already have a style for all buttons on bugzilla; i don't think there's value in making an exception here.
fair enough, thanks Byron.
 
I also wanted to ask that we mirror all the information entered in the first comment.  I'd like to simply keep a record of what was entered so that everything comes in with a consistent format.  And if things change, like due date, we can keep track of that.

So, for example, a consistent outline in comment #0, like:

>>Project/Request Title:
blah blah blah


>>Project Overview:
blah blah blah blah blah


>>Creative Specs & Deliverables:
blah blah


>>Launch Date:
xx/xx/xx


>>Creative Due Date:
xx/xx/xx


>>Mozilla Goal:
xx/xx/xx

>>Points of Contact:
etc etc.


Perhaps anything that isn't entered in will just default to "none entered" or "TBD" or something like that. What do you think?
attaching header graphic here.
Thanks Lee! 
Byron / David, please let me know if you have any questions.  Huge thanks again for everything so far. Your help is really appreciated and is going to make a big difference to us and our process.
Hi guys, Happy Monday!  Just wanted to check in on this to see if you had an ETA or an updated link for the form on stage? I realize there were a lot of changes so I totally understand you need time to create it.  But a quick update would be great so we can plan accordingly.  Thanks again.
I have uploaded an updated version of this new form to our test instance for your feedback.

https://bugzilla-dev.allizom.org/enter_bug.cgi?product=Mozilla&format=creative

Give it a try

dkl
Flags: needinfo?(tshahian)
I can't seem to use that link, it gives me an error, can we try again?

" Sorry, either the product Mozilla does not exist or you aren't authorized to enter a bug into it. "
Flags: needinfo?(tshahian)
(In reply to Tara (musingt) from comment #23)
> I can't seem to use that link, it gives me an error, can we try again?
> 
> " Sorry, either the product Mozilla does not exist or you aren't authorized
> to enter a bug into it. "

My fault. Proper link:

https://bugzilla-dev.allizom.org/enter_bug.cgi?product=Marketing&format=creative

dkl
Flags: needinfo?(tshahian)
Hi David, thanks again for this.  Looking great, and almost there.... 

Is it possible to make a few additional tweaks to bring this closer to the mockup I had attached? Specifically: 


* Making sure that the line-length and text box are aligned so that the text doesn't roll on way beyond the box? 
* Adding a bit of padding to the left margin so that it's not so tight against the edge of the page? 
* Is it possible to tint the background color to the specified color? 

Here is that mockup again:
https://bug864504.bugzilla.mozilla.org/attachment.cgi?id=749064

Please let me know, huge thanks once again.
Flags: needinfo?(tshahian)
(In reply to Tara (musingt) from comment #25)
> * Is it possible to tint the background color to the specified color? 

while possible, bugzilla has multiple skins and has a consistent look across all its pages.  sorry, but again i don't think we should be making an exception here, as it would complicate things when we make changes to our skins.

on a positive note, when we get the cycles we'll be completing the mozilla skin and making it the default, which will make all of bugzilla (including your form) much prettier.  you can use it now by changing the skin in your preferences.
(In reply to Tara (musingt) from comment #25)
> Hi David, thanks again for this.  Looking great, and almost there.... 
> 
> Is it possible to make a few additional tweaks to bring this closer to the
> mockup I had attached? Specifically: 
> 
> 
> * Making sure that the line-length and text box are aligned so that the text
> doesn't roll on way beyond the box? 
> * Adding a bit of padding to the left margin so that it's not so tight
> against the edge of the page? 
> * Is it possible to tint the background color to the specified color? 
> 
> Here is that mockup again:
> https://bug864504.bugzilla.mozilla.org/attachment.cgi?id=749064
> 
> Please let me know, huge thanks once again.

Thanks for the feedback. I have made some adjustments and uploaded a new revision for you to look at. I agree with glob in that we will hold off on some of the more custom changes such as changing the background color as we try to maintain a consistent look for other forms in Bugzilla. Let me know if it looks better with what I have done.

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

dkl
Flags: needinfo?(tshahian)
Thanks David, and Byron. Fwiw the customization requests stemmed partly because you had mentioned that the template was customizable :) that we could start with the template and pretty much change from there as needed.  So if this is as far as we can push it, then we can keep it there and tweak later when the time comes.

Even little things, like adding a little more padding between the text and the input fields help the form feel more welcoming. 

Looking at this again, it seems like we could optimize the text a bit so it's not as wordy.  We have revised copy on this etherpad: https://etherpad.mozilla.org/CreativeInitiationForm

If you can please make another update, we should then be good to go. 
Thanks again.
Flags: needinfo?(tshahian)
oh, and lastly:

please be sure that when the bug is filed, the auto=cc list includes:

* John slater
* kristin baird
* jennifer balaco
* lizz noonan
* and me.
(In reply to Tara (musingt) from comment #29)
> oh, and lastly:
> 
> please be sure that when the bug is filed, the auto=cc list includes:
> 
> * John slater
> * kristin baird
> * jennifer balaco
> * lizz noonan
> * and me.

+ gregory jost
Thanks for the feedback. I have made the wording adjustments and also added additional padding.

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

dkl
Flags: needinfo?(tshahian)
Thanks David. 

Can you please be sure that the people I listed are auto cc-ed to the bug? It doesn't look to be that way right now. That list is:

* Tara Shahian
* John Slater
* Kristin Baird
* Gregory Jost
* Jen Balaco
* Lizz Noonan

Also, if it's possible, can we have the empty fields auto-populate to a "N/A" or "Not provided" or something similar? if not, that's ok. just asking.

thanks again for all your help. we are really almost there. looking forward to getting this live soon.
Flags: needinfo?(tshahian)
(In reply to Tara (musingt) from comment #32)
> Thanks David. 
> 
> Can you please be sure that the people I listed are auto cc-ed to the bug?
> It doesn't look to be that way right now. That list is:
> 
> * Tara Shahian
> * John Slater
> * Kristin Baird
> * Gregory Jost
> * Jen Balaco
> * Lizz Noonan
> 

Sorry fixed.

> Also, if it's possible, can we have the empty fields auto-populate to a
> "N/A" or "Not provided" or something similar? if not, that's ok. just asking.

Sure. Will do a quick revision and put it up for feedback.

dkl
Hopefully this is it :) Please take a look at:

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

dkl
Flags: needinfo?(tshahian)
Looks great. let's book it! 

Follow up question (perhaps I need to file a new bug)
Can we add a new "product" category under the new bug list? we have "marketing" right now, which technically houses the design/copy components, but we want folks to go through to the form when filing brand engagement requests.  Can we add that in the list under 'marketing' and point to the engagement form? please let me know the process for that.  thankss!!!!!!!!!
Flags: needinfo?(tshahian)
(In reply to Tara (musingt) from comment #35)
> Follow up question (perhaps I need to file a new bug)
> Can we add a new "product" category under the new bug list? we have
> "marketing" right now, which technically houses the design/copy components,
> but we want folks to go through to the form when filing brand engagement
> requests.  Can we add that in the list under 'marketing' and point to the
> engagement form? please let me know the process for that.  thankss!!!!!!!!!

Most likely this will be better for a new bug report. To clarify, are you asking for your own complete product in Bugzilla (similar to Marketing) or to just create a new more specific component under Marketing such as "Brand Engagement" and then have the new form use that component instead?

New form committed and will be in the next production code push.

Committing to: bzr+ssh://dlawrence%40mozilla.com@bzr.mozilla.org/bmo/4.2
modified .htaccess
added extensions/BMO/template/en/default/bug/create/comment-creative.txt.tmpl                                                                             added extensions/BMO/template/en/default/bug/create/create-creative.html.tmpl                                                                            added extensions/BMO/web/images/creative.png
Committed revision 8843.  

dkl
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
OS: Mac OS X → All
Hardware: x86 → All
Resolution: --- → FIXED
(In reply to David Lawrence [:dkl] from comment #36)

> 
> Most likely this will be better for a new bug report. To clarify, are you
> asking for your own complete product in Bugzilla (similar to Marketing) 

yes !

or
> to just create a new more specific component under Marketing such as "Brand
> Engagement" and then have the new form use that component instead?
> 
> New form committed and will be in the next production code push.

Thanks! would that be this Thursday?
Blocks: 883946
Hi there. Can you please let me know / confirm that this link is live? If so, what is the link? Thanks.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
it's live at https://bugzilla.mozilla.org/form.creative
Status: REOPENED → RESOLVED
Closed: 7 years ago7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.