Closed Bug 832031 Opened 11 years ago Closed 11 years ago

Project Kickoff Form: Add "PO Needed?" when "<=$25,000" is selected under "Vendor Cost"

Categories

(bugzilla.mozilla.org Graveyard :: Extensions: MozProjectReview, defect)

Production
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: winnie, Assigned: dkl)

References

Details

Currently if "yes" is selected for "Separated Party", "Vendor Cost" populates.

1. Please add a new dropdown "Yes/No" for "PO Needed?" if "<$25,000" is selected under "Vendor Cost".
   a. If "Yes" is selected, create a Finance bug.
   b. If "No" is selected, current process stays, nothing is needed.
Added Michelle to the bug as well.
Can we make sure all non-trivial change to the kick off form go to stage first for testing? I want to minimize the chance we introduce a bug that breaks functionality of the form since we're now live.

Winnie,
Within stage can you run through a few different tests to make sure:
1. your new functionality works
2. the other group bugs are triggered in at least one test?

Thanks
No longer depends on: 818249
Assignee: nobody → dkl
Status: NEW → ASSIGNED
Changes have been pushed out for feedback. Let me know if it looks good.

https://bugzilla-stage-tip.mozilla.org/form.moz.project.review

Seems the DB is down currently, but the changes should be there when it comes back up.

dkl
Flags: needinfo?(waoieong)
Michael - Will definitely test to make sure other group bugs will be generated.

David - I will wait when the DB is up again. Just tried and it's still down.

Thanks, Winnie
Flags: needinfo?(waoieong)
DB is still down. When can I test this? Thanks dkl!
(In reply to Winnie Aoieong from comment #5)
> DB is still down. When can I test this? Thanks dkl!

Back now. Please test.

dkl
Tested in stage and created bug 686799. It only opened a legal bug 686800 but not a Finance bug. Can you check?
(In reply to Winnie Aoieong from comment #7)
> Tested in stage and created bug 686799. It only opened a legal bug 686800
> but not a Finance bug. Can you check?

Found a bug or two that needed to be fixed and has not been pushed out for testing. Please try again.

Thanks
dkl
Tested and this time works.

Generated master bug# 686821 and created dependent bugs 686822 to 686826. This works great and thanks!

A separate enhancement request - Right now the the master bug shows all the dependent bug numbers but an user will not know what these bugs are unless they click on each of them. Can we add the description of what type of bug next to the bug number? E.X. Security Bug - 686822, Finance Bug - 686824?

Thanks!
(In reply to Winnie Aoieong from comment #9)
> Tested and this time works.
> 
> Generated master bug# 686821 and created dependent bugs 686822 to 686826.
> This works great and thanks!
> 
> A separate enhancement request - Right now the the master bug shows all the
> dependent bug numbers but an user will not know what these bugs are unless
> they click on each of them. Can we add the description of what type of bug
> next to the bug number? E.X. Security Bug - 686822, Finance Bug - 686824?
> 
> Thanks!

If you mouse over the bug ids in the master bug page, a box displays the summary of the bug you are hovering over. The summary should explain enough about what the bug is for.

dkl
(In reply to David Lawrence [:dkl] from comment #10)
> (In reply to Winnie Aoieong from comment #9)
> > Tested and this time works.
> > 
> > Generated master bug# 686821 and created dependent bugs 686822 to 686826.
> > This works great and thanks!
> > 
> > A separate enhancement request - Right now the the master bug shows all the
> > dependent bug numbers but an user will not know what these bugs are unless
> > they click on each of them. Can we add the description of what type of bug
> > next to the bug number? E.X. Security Bug - 686822, Finance Bug - 686824?
> > 
> > Thanks!
> 
> If you mouse over the bug ids in the master bug page, a box displays the
> summary of the bug you are hovering over. The summary should explain enough
> about what the bug is for.
> 
> dkl

That works except when you don't have access to the bug - like legal bugs. That's the main driver for the enhancement request. When there are several bugs that users don't have access to it's hard to tell if the kickoff form functioned correctly.
(In reply to Michael Coates [:mcoates] from comment #11)
> > If you mouse over the bug ids in the master bug page, a box displays the
> > summary of the bug you are hovering over. The summary should explain enough
> > about what the bug is for.
> > 
> > dkl
> 
> That works except when you don't have access to the bug - like legal bugs.
> That's the main driver for the enhancement request. When there are several
> bugs that users don't have access to it's hard to tell if the kickoff form
> functioned correctly.

One option that would not be difficult to implement would be to simply add a second comment to the main project bug, which has each of the created bugs and the summaries listed. The bug ids will be hyper linked but the mouse over summary will still be filtered. Sound reasonable?

dkl
Flags: needinfo?(mcoates)
(In reply to David Lawrence [:dkl] from comment #12)
> (In reply to Michael Coates [:mcoates] from comment #11)
> > > If you mouse over the bug ids in the master bug page, a box displays the
> > > summary of the bug you are hovering over. The summary should explain enough
> > > about what the bug is for.
> > > 
> > > dkl
> > 
> > That works except when you don't have access to the bug - like legal bugs.
> > That's the main driver for the enhancement request. When there are several
> > bugs that users don't have access to it's hard to tell if the kickoff form
> > functioned correctly.
> 
> One option that would not be difficult to implement would be to simply add a
> second comment to the main project bug, which has each of the created bugs
> and the summaries listed. The bug ids will be hyper linked but the mouse
> over summary will still be filtered. Sound reasonable?
> 
> dkl

That's perfect. So the summaries of the dependent bugs filed would be explained as a comment within the master bug. Sounds great.
Flags: needinfo?(mcoates)
(In reply to Michael Coates [:mcoates] from comment #13) 
> > One option that would not be difficult to implement would be to simply add a
> > second comment to the main project bug, which has each of the created bugs
> > and the summaries listed. The bug ids will be hyper linked but the mouse
> > over summary will still be filtered. Sound reasonable?
> > 
> > dkl
> 
> That's perfect. So the summaries of the dependent bugs filed would be
> explained as a comment within the master bug. Sounds great.

Cool. Bug 835212.

dkl
dkl - since the original ask of this bug is now tested and works, can you push this to production? we already have another bug opened for the other enhancement request. 

thanks, winnie
Committing to: bzr+ssh://dlawrence%40mozilla.com@bzr.mozilla.org/bmo/4.0             
modified extensions/MozProjectReview/Extension.pm
modified extensions/MozProjectReview/template/en/default/bug/create/comment-moz-project-review.txt.tmpl                                                                      
modified extensions/MozProjectReview/template/en/default/bug/create/create-moz-project-review.html.tmpl
modified extensions/MozProjectReview/web/js/moz_project_review.js
Committed revision 8464.

Committing to: bzr+ssh://dlawrence%40mozilla.com@bzr.mozilla.org/bmo/4.2             
modified extensions/MozProjectReview/Extension.pm
modified extensions/MozProjectReview/template/en/default/bug/create/comment-moz-project-review.txt.tmpl                                                                      
modified extensions/MozProjectReview/template/en/default/bug/create/create-moz-project-review.html.tmpl                                                                      
modified extensions/MozProjectReview/web/js/moz_project_review.js
Committed revision 8529.

Cool. Will be in the next code push.
dkl
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Product: bugzilla.mozilla.org → bugzilla.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.