Closed Bug 1121594 Opened 5 years ago Closed 4 years ago

Mozilla Recruiting Requisition Opening Process Template

Categories

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

Production
x86
macOS
defect
Not set

Tracking

()

RESOLVED FIXED

People

(Reporter: rberenbaum, Assigned: dylan, Mentored)

Details

Attachments

(2 files, 6 obsolete files)

Hello,

The Requisition opening process for HR and Recruiting is being transferred to being hosted on Bugzilla. We will need to create a template (much like Legal's template, here: https://bugzilla.mozilla.org/enter_bug.cgi?product=Legal).

The opening text needs to be as follows: (currently in dev)

The required fields for the form are as follows:

Position Title
Cost Center (select from cost center list)
Hiring Manager Name:
VP Authority (select from list of VPs):
HRBP Name (select from: Joanne Nguyen, Jess Amann, Michael Aukland)
Full time or Seasonal?
Desired Location
Comp Grade

The "your request has been successfully submitted!" page should read as follows: 
Thank you for submitting your request to have a requisition opened! It will be reviewed by the VPs and prioritized according to needs across the organization. If you have any questions please reach out to Michelle Marovich (mmarovich@mozilla.com). 

The bugs themselves should have the same security setting as a Legal bug. Also, we need to know how to set up the distribution list for this product. 

Please reach out to Michelle Marovich if you have any questions. Thank you!
Assignee: administration → nobody
Product: Bugzilla → bugzilla.mozilla.org
QA Contact: default-qa
Version: unspecified → Production
Component: Administration → Custom Bug Entry Forms
Hi Rachel, is there a deadline for your project?  The Bugzilla devs are currently concentrating on their Q1 deliverables, so it might be a couple weeks before we get to this request.
Flags: needinfo?(rberenbaum)
Hi Mark,


No roles will get opened and prioritized for  2015 hiring until we have this.  So it's a fairly high priority.
Okay, but in the future, please give us some advance notice for high-priority items like this so we can fit them into our schedules.  We have a relatively small team with many incoming requests and our own goals.

Also, Rachel says (if I understand correctly) that the form design is in dev right now.  When will that be finalized?  From experience, having to do a lot of adjustments to the form's content while we are working on it significantly draws out the process.
Assignee: nobody → dylan
Flags: needinfo?(rberenbaum)
Priority: -- → P1
Hi Mark,

Form design is complete, to clarify the part I described as "in dev" is the opening text- completed, here:

"Recruiting Bugs are visible only to the Reporter, members of the People Team, and those on the CC list. Please do not add non-employees to the CC list. This form is to request a new open requisition only, and is not for communication about existing open requisitions in Jobvite. <b>Do not put information about backfills or replacements directly into this bug.</b>.

Thank you for all of your help (and your team's!)
Assignee: dylan → nobody
Priority: P1 → --
Hi Mark, 

I really appreciate you scrambling, and we will work hard to make this our only fire drill for your team.    If there are changes in the future, they will be communicated with plenty of lead time ( weeks). 

Our side of things has weird cadences and time frames, driven by the SCVP level ( especially around opening headcount at the beginning of the year) and that can sometimes create urgency where previously none existed.  

So thank you.  We totally owe you.
We'll aim to have this done in time for our next deployment, which should be next Monday night or Tuesday morning.
And thank you for the explanation. :)
Assignee: nobody → dylan
Status: NEW → ASSIGNED
Thank you Mark and Dylan! Like Michelle said, we totally owe you! :)

Unfortunately we do have one small edit- we'd like to add a question to the "form" after the 'Full time or Seasonal question', as follows:

Will you be hiring more than one of this role in 2015? (Yes/No)
And hopefully final edit from David Slater:

What part of your strategic plan does this role impact?  [open paragraph box]
Why is this critical for success? [open paragraph box]

Is this new headcount or backfill?  [drop down, net new/backfill]
Currently I'm using a new "HR and Recruiting" product for this. Should this get its own product? 
I hope to have this in for review and up on bugzilla-dev for testing shortly.
Flags: needinfo?(rberenbaum)
Hi Dylan,

I'd appreciate it if you called this product Recruiting.  

How/when do we identify who on this product gets notified when a new bug is filed?   Also, let's move this convo to the bug so that it gets out of the black box that is my email?
(In reply to Michelle Marovich from comment #11)
> Hi Dylan,
> 
> I'd appreciate it if you called this product Recruiting.  
Excellent, this is the name I have used.

> How/when do we identify who on this product gets notified when a new bug is
> filed?   Also, let's move this convo to the bug so that it gets out of the
> black box that is my email?

Component watching would be the recommended method. Interested parties would
need to go to https://bugzilla.mozilla.org/userprefs.cgi?tab=component_watch
and choose to watch the Recruiting product (which will only have a single component, "General").
Attached patch bug-1121594-v1.patch (obsolete) — Splinter Review
How does this look, aside from the place holder text in the Cost Center and VP Authority sections?
Attachment #8549973 - Flags: review?(dkl)
I am embarrassed to ask, but: Where can I get the list of Cost Centers and VPs?
Flags: needinfo?(mmarovich)
I got Dylan the Cost Center list.  Isn't each Cost Center assigned to a particular VP, though?  If so, do we need the "VP Authority" field?
When I use these bugs to pull reports for prioritizations, having the VP field will allow me to sort more easily than by cost center.  

If it's too hard to add, we can work around it, but it's on the list of requests from Dave Slater. 

Let me double check and make sure you have an updated cost center list, they just put a new one out... in the last two weeks.
Flags: needinfo?(mmarovich)
Added most current cost center list.
Sylvie-- can you add a list of current VP's as an attachment?  It's the only thing I don't have, and I figure you have one.
Flags: needinfo?(rberenbaum) → needinfo?(sbrossard)
Comment on attachment 8549973 [details] [diff] [review]
bug-1121594-v1.patch

Review of attachment 8549973 [details] [diff] [review]:
-----------------------------------------------------------------

1. Don't forget the changes needed for .htaccess (form.recruiting)
2. Either designate using a colored asterisk that the fields are mandatory or add a line of text stating that all fields are mandatory.
3. Personally for small forms, I like the two line approach per field. Example: https://bugzilla.mozilla.org/form.web.bounty
4. You will need a template for showing the successful submission. For example, see extensions/BMO/template/en/default/bug/create/created-fxos-betaprogram.html.tmpl.
5. Need javascript to enforce the required fields (or use HTML5 required attribute).

::: extensions/BMO/template/en/default/bug/create/create-recruiting.html.tmpl
@@ +36,5 @@
> +
> +<p>
> +  Recruiting [% terms.Bugs %] are visible only to the Reporter, members of the People
> +  Team, and those on the CC list. Please do not add non-employees to the CC list.
> +  This form is to request a new open requisition only, and is not for

Set a max width for this text to 60-70%.

@@ +38,5 @@
> +  Recruiting [% terms.Bugs %] are visible only to the Reporter, members of the People
> +  Team, and those on the CC list. Please do not add non-employees to the CC list.
> +  This form is to request a new open requisition only, and is not for
> +  communication about existing open requisitions in Jobvite. <strong>Do not put
> +  information about backfills or replacements directly into this [% terms.bug %].</strong>

Put the <strong> portion in its own paragraph.

@@ +58,5 @@
> +
> +  <table>
> +    <tr>
> +      <td align="right" valign="top">
> +        <strong>Position Title:</strong>

Can you use <th> here instead of <strong>?

@@ +70,5 @@
> +      <td align="right">
> +        <strong>Cost Center:</strong>
> +      </td>
> +      <td>
> +        <select id="cost_center" name="cost_center">

When dealing with required drop downs, I like to add an additional option <option value="">Select</option> which makes the JS easier for enforcing.
Attachment #8549973 - Flags: review?(dkl) → review+
Here is the list of VPs:

Rick Fant
Sylvie Veilleux
Mark Mayo
Johnath Nightingale
Pete Scanlon
Mary Ellen Muckerman
Darren Herman

Additionally , here is the list of Steering Committee members:

Chris Beard
Denelle Dixon Thayer
David Slater
Andreas Gal
Jim Cook
Li Gong
Flags: needinfo?(sbrossard)
Comment on attachment 8549973 [details] [diff] [review]
bug-1121594-v1.patch

Review of attachment 8549973 [details] [diff] [review]:
-----------------------------------------------------------------

Sorry. Meant r- on this, not r+ :(
Attachment #8549973 - Flags: review+ → review-
Attached patch bug-1121594-v2.patch (obsolete) — Splinter Review
> 1. Don't forget the changes needed for .htaccess (form.recruiting)
Done.
> 2. Either designate using a colored asterisk that the fields are mandatory
> or add a line of text stating that all fields are mandatory.
Done, like the other forms.

> 3. Personally for small forms, I like the two line approach per field.
I think it would be useful to see if the current way (which is a copy of the Legal form) is acceptable to our users.

> 4. You will need a template for showing the successful submission. For
> example, see
> extensions/BMO/template/en/default/bug/create/created-fxos-betaprogram.html.
> tmpl.
Right! I didn't know how we did that. You also have to set the created-format form paramter. Thanks!

> 5. Need javascript to enforce the required fields (or use HTML5 required
> attribute).
Using html5 required seems to work, provided I add the empty default select-options.

The rest of the changes brought up in review are also fixed.
Attachment #8549973 - Attachment is obsolete: true
Attachment #8550434 - Flags: review?(dkl)
Comment on attachment 8550434 [details] [diff] [review]
bug-1121594-v2.patch

Review of attachment 8550434 [details] [diff] [review]:
-----------------------------------------------------------------

r=dkl

::: extensions/BMO/template/en/default/bug/create/create-recruiting.html.tmpl
@@ +31,5 @@
> +}
> +p {
> +   max-width: 40%;
> +}
> +label.required:after {

Personally I think it looks better with the red asterisk before the label as this allows Cc: to line up properly with the other labels.

label.required:before {
  content: "* ";
  color: red;
}

@@ +195,5 @@
> +        <th align="right" valign="top">
> +          <label class="required" for="comp_grade">Comp Grade:</label>
> +        </th>
> +        <td>
> +          <input required name="comp_grade" id="comp_grade" size="60" value="[% comp_grade FILTER html %]">

Might as well leave the value="" blank as comp_grade is not passed in by enter_bug.cgi. Same with the other non-standard names.
Attachment #8550434 - Flags: review?(dkl) → review+
(In reply to David Lawrence [:dkl] from comment #23)

> Might as well leave the value="" blank as comp_grade is not passed in by
> enter_bug.cgi. Same with the other non-standard names.

Foiled by copying Legal again. Thanks!
Form up on the dev site for the relevant people to check / comment on:

https://bugzilla-dev.allizom.org/enter_bug.cgi?product=Recruiting
Flags: needinfo?(mmarovich)
To ssh://gitolite3@git.mozilla.org/webtools/bmo/bugzilla.git
   f2112d4..6279e60  master -> master
Hey Dylan, 

Ok, round of feedback from the whole team using the component.  We've got the following edit requests ( so sorry) and then we should be good.  
 Initial request:  
Position Title
Cost Center (select from cost center list)
Hiring Manager Name:
VP Authority (select from list of VPs):
HRBP Name (select from: Joanne Nguyen, Jess Amann, Michael Aukland)
Full time or Seasonal?
Desired Location
Comp Grade

Directly after that, new requests:

1. Is this new headcount or backfill? [DROP DOWN: net new/backfill].

2. Question add: In the box below, please upload or copy/paste a draft of the Job Description you would like to be associated with this requisition. [TEXT BOX with ADD FILE upload option].

3. Question add: What part of your strategic plan does this role impact? [OPEN PARAGRAPH BOX]

4. Why is this critical for success? [OPEN PARAGRAPH BOX]

5. Formatting: center form, like Legal Bug.

Thanks so much for all your work on this.  Sorry about the delay in response, I was on PTO and it was a holiday in the US.
Flags: needinfo?(mmarovich)
I meant to update this yesterday -- we didn't get a push this week, but we should be good for pushing this next week.
Hi Dylan, 

thanks for the update-- just wanted to make sure you saw the changes requested in comment 27?
(In reply to Michelle Marovich from comment #29)
> Hi Dylan, 
> 
> thanks for the update-- just wanted to make sure you saw the changes
> requested in comment 27?

Yep! The form is available at https://bugzilla-dev.allizom.org/enter_bug.cgi?product=Recruiting for review again.
Hey Dylan! 

Looks great.  One thing though, you have two questions about it being new or backfill.  Fix that and I think we are good to go!


Do you know if this will get pushed this week?  If so I'll talk about it at the MoCo meeting tomorrow.
Yes, it will be pushed tonight or tomorrow morning.
Attached patch bug-1121594-v3.patch (obsolete) — Splinter Review
Attachment #8550434 - Attachment is obsolete: true
Attachment #8554701 - Flags: review?(dkl)
Comment on attachment 8554701 [details] [diff] [review]
bug-1121594-v3.patch

Review of attachment 8554701 [details] [diff] [review]:
-----------------------------------------------------------------

::: extensions/BMO/template/en/default/bug/create/create-recruiting.html.tmpl
@@ +220,5 @@
> +      </tr>
> +
> +      <tr>
> +        <th align="right" valign="top">
> +          <label class="required" for="new_or_backfill">Is this new headcount or backfill?</label>

You have this question twice. Also why is it not a drop down with "New" and "Backfill" as the choices? Doesn't seem to fit with a free text input.

@@ +228,5 @@
> +        </td>
> +      </tr>
> +
> +      <tr>
> +        <th align="right" valign="top">

These <th> should all be <td> with CSS classes which I should have mentioned long ago but not a show-stopper.

@@ +260,5 @@
> +      </tr>
> +
> +      <tr>
> +        <th align="right" valign="top">
> +          <label for="plan_impact">What part of your strategic plan does this role impact?</label>

This label is displayed twice, here and below.
Attachment #8554701 - Flags: review?(dkl) → review-
Attached patch bug-1121594-v3.patch (obsolete) — Splinter Review
Let me try uploading the right file (although the select box was an oversight, the obvious text problem should have been correct.)
Attachment #8554701 - Attachment is obsolete: true
Attachment #8554722 - Flags: review?(dkl)
Attached patch bug-1121594-v3.patch (obsolete) — Splinter Review
Attachment #8554722 - Attachment is obsolete: true
Attachment #8554722 - Flags: review?(dkl)
Attachment #8554725 - Flags: review?(dkl)
Attachment #8554725 - Attachment is obsolete: true
Attachment #8554725 - Flags: review?(dkl)
Attached patch bug-1121594-v3.9.patch (obsolete) — Splinter Review
Attachment #8554728 - Attachment is obsolete: true
Comment on attachment 8554731 [details] [diff] [review]
bug-1121594-v3.99.patch

After about as many technical hangups as I should allotted for a week, here's the patch that actually needs to reviewed, without added cruft from the divergence of master and this branch.
Attachment #8554731 - Flags: review?(dkl)
Comment on attachment 8554731 [details] [diff] [review]
bug-1121594-v3.99.patch

Review of attachment 8554731 [details] [diff] [review]:
-----------------------------------------------------------------

Fix on commit. r=dkl

::: extensions/BMO/template/en/default/bug/create/create-recruiting.html.tmpl
@@ +224,5 @@
> +          <label class="required" for="new_or_backfill">Is this new headcount or backfill?</label>
> +        </th>
> +        <td>
> +          <select required name="new_or_backfill" id="new_or_backfill">
> +            <option>Select...</option>

<option value="">Select...</option>
Attachment #8554731 - Flags: review?(dkl) → review+
To ssh://gitolite3@git.mozilla.org/webtools/bmo/bugzilla.git
   d645d21..cd92366  master -> master
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
the "recruiting" product still needs to be created on stage and production.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
https://bugzilla.mozilla.org/form.recruiting is now live.

leaving this bug open as the product was created with placeholders for descriptions.
Hey!  The description should read:

Request that we prioritize and open a headcount for hiring.
When I go to add myself to watch this component, it's not in the drop down.  I'm assuming it just hasn't fully populated yet?
(In reply to Michelle Marovich from comment #45)
> When I go to add myself to watch this component, it's not in the drop down. 
> I'm assuming it just hasn't fully populated yet?

You must not be in the hr group, checking on that now and I'll report back what I find.
Yep,  we should figure out who all is in that group.  Because it's changed a lot lately.  Let me know the list and I'll figure out how to get a corrected one?
Currently, members of group hr appear is jcook@mozilla.com
group hr is not a member of other groups, so that should be the full list.
Hahahahahahaha!

Ok, let me get you a list. I'm on a train, and it's too hard to do from my phone.  I'll have it to you by 9 pacific.
(In reply to Michelle Marovich from comment #49)
> Hahahahahahaha!
> 
> Ok, let me get you a list. I'm on a train, and it's too hard to do from my
> phone.  I'll have it to you by 9 pacific.

Excellent, I'll have to enter them one at a time but I'll do so as fast as possible.

The product description is updated.
Group: mozilla-employee-confidential
Woops, that was a mistake.
Group: mozilla-employee-confidential
I spoke with Michelle in IRC and she sent me an email of the people to add to the hr group. There doesn't appear to be a script to do this, so I have to edit each user by hand -- it'll take a little bit. will update bug when done.
Done! They should all be in the hr group now and able to see the new form.
Is everything satisfactory with this form?
So far so good!  However nothing survives the first engagement with the enemy.  Can we leave the bug open until EOB tmrw?  Just waiting to get final round of user feedback.
(In reply to Michelle Marovich from comment #55)
> So far so good!  However nothing survives the first engagement with the
> enemy.  Can we leave the bug open until EOB tmrw?  Just waiting to get final
> round of user feedback.

because this form has been pushed to production, it's better if you file a new bug for any further changes.  it makes things much easier to track should someone else work of those amendments.
Status: REOPENED → RESOLVED
Closed: 5 years ago5 years ago
Resolution: --- → FIXED
Hi Byron & Dylan,

Would you please update the VP list, removing Andreas Gal and adding Jascha KaykasWolff?

Thank you!
Rachel
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Tracking this request in bug 1172614. It'll be done in a jiffy.
Status: REOPENED → RESOLVED
Closed: 5 years ago4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.