1058615 - New Custom Bugzilla Form Needed For PR Team

Status: RESOLVED FIXED

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

Description

[Valerie Ponell]

Attachment: PR_Project_Bugzilla_Form_Sample.xlsx

Hi Bugzilla team,

per my email conversation with Byron Jones, the Mozilla PR team would like to have a new custom Bugzilla form to file and track internal PR
projects. This means that whenever someone from the PR starts a new
project, he or she would need to file a bug, so the whole team is aware
and can track the progress.

We have somewhat build the form with a Google Doc for now (just for us to practise as long as it takes to set the Bugzilla form up), in case this helps as a sample: https://docs.google.com/spreadsheets/d/1jtpCMjOn_S4Vws3SLkHuWHP7z0hq903c425JlMPq4As/edit#gid=163809590

An Excel sheet with all copy (for dropdown option etc) is also attached.

More details:

- Please mark bugs created with this form as confidential
- Mix of plain text, dropdown options, attachment upload and internal
(bugs) and externals links (e.g. to Basecamp or Google Docs). Some
fields need to be mandatory (please see Excel list attached or Link to Google Doc above)
- If possible, all PR bugs visible and accessible by all PR team members
per default (Byron suggested to create a Bugzilla security group for the PR team)

Bugzilla emails for the team members are:

Erica Jostedt (Administrator): [e-mail]
Laura Napoli: [e-mail]
Tristan Nitot: [e-mail] (and secondary if possible: [e-mail])
Barbara Hüppe: [e-mail]
Valerie Ponell (second Administrator if possible): [e-mail]
Karolina Shaw: [e-mail]
Mike Manning: [e-mail]
Paul Jarratt: [e-mail]
Aurelien Hubert: [e-mail]

- For dropdown options, if "other" is selected, please display a text field to capture the value

- For "Project Description", "Project Goals", "Key Messages" and "PR Goals" please display large (multi-line) text fields

- For "Ressources" please always display at least two fields (dropdown with "spokesperson/demo staff/creative support/other", and a text field. If "other" is selected, display a second text field)

- For "Project Owner" please display a freeform text field where we can enter a person's name (does not have to be a bugzilla user)

The old PR Bugzilla form can be killed or amended to the new version if that's easier (was for external requests from the PR team): https://bugzilla.mozilla.org/enter_bug.cgi?product=Mozilla%20PR&format=mozpr

Hope this makes sense! Thank you for your help in advance!

Valerie

Comment 1

[:glob ✱]

valerie,

i've deployed the first revision of the script onto our staging server:

https://bugzilla-dev.allizom.org/form.mozpr
you can view my testing bug at https://bugzilla-dev.allizom.org/show_bug.cgi?id=1004442


please have a play with the form, use it to create bugs, and let me know of any changes.

Comment 2

[Valerie Ponell]

Hi Byron,

this looks really great, thank you for putting this together for us so quickly!

I would just have three minor edits if that's okay (if the last one is too much work, no worries, we can leave that as it is):

> "PR Project Owner" dropdown: please add "Valerie Ponell" ([e-mail]), Justin O'Kelly ([e-mail]) and "Karolina Shaw" ([e-mail]) (sorry if I forgot to add them in the first place...:))

> Under "Details" below "Tier": please add "Project Type" with dropdown (Announcement, Speaking and Events, Planning, Messaging and Materials, Campaign, Other:plus freetext)

> "Press Center Update", "External ressources" and "Internal Resources": Could we perhaps have tick boxes instead of the dropdown, so we can select multiple options at the same time plus the "Other" freetext field (only if this is not too much work, otherwise leave as it is)

The rest looks great and I'm sure it will help us a lot! Thanks again for your magic, I love it :)

Valerie

Comment 3

[:glob ✱]

no problems with any of these edits..

> > Under "Details" below "Tier": please add "Project Type" with dropdown (Announcement, Speaking and Events, Planning, Messaging and Materials, Campaign, Other:plus freetext)

should this be a mandatory field?

> > "Press Center Update", "External ressources" and "Internal Resources": Could we perhaps have tick boxes instead of the dropdown, so we can select multiple options at the same time plus the "Other" freetext field (only if this is not too much work, otherwise leave as it is)

no worries, will do.

Comment 4

[Valerie Ponell]

Great - yes, please make "Project Type" a mandatory field.

\m/

THANKS!

Comment 5

[:glob ✱]

https://bugzilla-dev.allizom.org/form.mozpr has been updated.

Comment 6

[Valerie Ponell]

Perfect, thanks Byron! If it's not a problem, can we add "Other: plus freetext" to the "PR Owner" dropdown? With this change made, it looks good to go now and no need for another round of review. We are very excited, so thanks a lot for your great help with this! :)

Valerie

Comment 7

[:glob ✱]

\o/

To ssh://[e-mail]/webtools/bmo/bugzilla.git
   64808c8..e1d1c64  master -> master

Comment 8

[:glob ✱]

this form is now live: https://bugzilla.mozilla.org/form.mozpr

Comment 9

[Valerie Ponell]

Thanks Byron! Perhaps I did somethign wrong, but when I was trying to submit a test bug (just being paranoid that it might leak some confidential information, so wanted to amek sure it's private when filed), I got the following error message: 

"Invalid Component. There is no component named 'Projects' in the 'Mozilla PR' product. Please press Back and try again." (see screenhot)

Did I do anythign wrong?

Comment 10

[Valerie Ponell]

Attachment: Invalid Component.png

Comment 11

[:glob ✱]

oops; i forgot to add that component to production.  i've done that now; sorry about that.

Comment 12

[Valerie Ponell]

Great, works now Byron, thank you! I filed a test bug (https://bugzilla.mozilla.org/show_bug.cgi?id=1068533) and just wanted to double-check with you that: only PR team members can access an existing bug and nobody else (I tested this with two people and looks like it, but just wanted to double-check with you).

Also, when a new bug is filed, right now it is being send to no one. Can we add the whole PR team to the list of every new PR bug - these are:

Erica Jostedt: [e-mail]
Laura Napoli: [e-mail]
Tristan Nitot: [e-mail] 
Barbara Hüppe: [e-mail]
Valerie Ponell: [e-mail]
Karolina Shaw: [e-mail]
Mike Manning: [e-mail]
Paul Jarratt: [e-mail]
Aurelien Hubert: [e-mail]
Justin O'Kelly: [e-mail] (I realized I forgot to add him previously, so he should have access too)

Now, the PR bugs should show up on each members bug dashboard, correct? I am looking for a way for PR team members to keep track of the PR bugs, without being spammed by bugmail. Thus:

- Would you recommend that each person goes into the bug and ticks the box "Never email me to about this bug" after they were added to avoid bugmail overload? Or would you recommend that whoever files a bug needs to add the PR members manually instead of per default?

- Where would you recommend we would find all PR bugs the easiest way in My Dashboard? Would it be "My Dashboard" > "Choose Query" > which one to pick? Would it be possible to add "PR team bugs" as a query to the dropdown here, or are the lists here generated automatically only? If each PR team member would be added as a "Mentor" per default (I have never been added as a mentor, so don't know how this shows up), would this make the listing of PR bugs easier (as probably everyones "mentor" list is empty compared to the other lists, e.g. "you are CC'd one etc).

Sorry for all the additional questions :) And thanks a lot for your help and patience with this :)

Valerie

Comment 13

[:glob ✱]

(In reply to Valerie Ponell from comment #12)
> Also, when a new bug is filed, right now it is being send to no one.

please instruct the team to use "component watching" to watch the "Projects" component:
https://bugzilla.mozilla.org/userprefs.cgi?tab=component_watch
more on this below..

> Now, the PR bugs should show up on each members bug dashboard, correct?

the dashboard provides many views.  by default it'll only show bugs which are assigned to you.
the bugs created by this form are not assigned initially assigned to anyone.


> I am looking for a way for PR team members to keep track of the PR bugs, without
> being spammed by bugmail.

the configuration i'd suggest is for everyone to receive emails for new bugs only, _except_ if they are the assignee, where they should receive emails for all changes to the bug.  anyone who wants a view of all the open bugs in the component can build a query and add it to the dashboard.

note: don't use the "mentor" field, because you're not acting as mentors for these bugs and it would confuse people and other systems.



ok, to set up email you first tell bugzilla you want to receive email for all changes in the "projects", then apply a filter to drop most emails.

1. use component watching

https://bugzilla.mozilla.org/userprefs.cgi?tab=component_watch&product=Mozilla%20PR&component=Projects
you want to watch the "Projects" component within the "Mozilla PR" product (should be pre-selected when you load that url).


2. use bugmail filtering

https://bugzilla.mozilla.org/userprefs.cgi?tab=bugmail_filter

now we need to configure bugzilla to ignore all email, except for what we're interested in (new bugs and bugs that as assigned to me).

we need to add 2 filters - first "exclude all emails in this component where i'm not the assignee", and then an include filter which overrides that condition when a bug is created:

FIELD       | PRODUCT    | COMPONENT | RELATIONSHIP | ACTION
__Any__     | Mozilla PR | Projects  | Not Assignee | exclude
Bug Created | Mozilla PR | Projects  | __Any__      | include



anyone who wants a list of open PR project bugs on their dashboard will have to perform the following steps:

3. create a saved search

3a. build the query you want to display on the dashboard (eg. http://mzl.la/1wGFcPV)
3b. "remember search" with a name (i give it the name "Open PR Projects")
3c. add it to the dashboard:
    https://bugzilla.mozilla.org/userprefs.cgi?tab=saved-searches
    check the "My Dashboard" checkbox next to the search we just saved

Comment 14

[Valerie Ponell]

Ha, I managed to create the filters and to add the saved search to my dashboard :) Thanks a lot for your instructions! Will now share this with the PR team - we might have another one or two stupid questions for you as we get to know Bugzilla better, but for now we should be good :) Again, THANKS for your great help and your patience!

Comment 15

[Valerie Ponell]

Hi Byron - actually I just came across one more question :) If all Bugmail filters are set accordingly, do I understand right that the person filing the bug does NOT have to add anyone from the PR team manually to it, correct? And that you don't have to add the whole team per default on each PR Project Bug? When the second mentioned filter above is set correct to "Relationship > Any", then the Bugmail is sent out automatically, once the bug is filed, correct?

THANKS!

Comment 16

[:glob ✱]

(In reply to Valerie Ponell from comment #15)
> If all Bugmail filters are set accordingly, do I understand right that the
> person filing the bug does NOT have to add anyone from the PR team manually to it,
> correct?

correct - the component watching configuration takes care of sending notifications.

> And that you don't have to add the whole team per default on each
> PR Project Bug? When the second mentioned filter above is set correct to
> "Relationship > Any", then the Bugmail is sent out automatically, once the
> bug is filed, correct?

the filters apply to all bugmail, including those created by component watching.

we have two rules - the first excludes *all* email for bugs that are not assigned to you.  if we only had that rule in place you wouldn't receive new bug notifications because by default your bugs are assigned to nobody.  we need a second "include" rule to allow the new bug notifications through.

Comment 17

[Valerie Ponell]

Okay, perfect - thanks Byron! \m/