Closed Bug 571125 Opened 14 years ago Closed 14 years ago

Web Dev Project Initiation Form

Categories

(Websites :: Other, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: malexis, Assigned: skeen.bugzilla)

References

()

Details

Attachments

(1 file)

Web Dev is developing a web form for project initiation. Project owners will provide project details and submit.

Here is the document outlining required fields
https://docs.google.com/Doc?docid=0AQf0FGHoPL05ZGc3bXpnNHNfMTNjMnBrcWRkNQ&hl=en

Need to find a home for this. I will set up a time to discuss requirements in more detail.
Assignee: nobody → skeen.bugzilla
Mike, what can we fix in Gecko to help with this?
Component: General → Other
Product: Core → Websites
QA Contact: general → other
Version: unspecified → other
Gecko is okay, bz.  As you were.  :)
I tweaked the doc and all the information/required fields are in place:
https://docs.google.com/Doc?docid=0AQf0FGHoPL05ZGc3bXpnNHNfMTNjMnBrcWRkNQ&hl=en

"Submit" will generate top-level Bugzilla ticket. We still need to decide whether any fields will trigger/create dependency bugs.

On Friday we discussed there is no need for a db to store data. data will exist in bugzilla.

Form will live on intranet.

Sam says he can reuse code from Worker Management form.
Thx Mike,
I added a few clarifying questions to https://docs.google.com/Doc?docid=0AQf0FGHoPL05ZGc3bXpnNHNfMTNjMnBrcWRkNQ&hl=en
thx sam,
I updated the doc. hit me up here or IRC (malexis) if any more clarification is needed.

https://docs.google.com/Doc?docid=0AQf0FGHoPL05ZGc3bXpnNHNfMTNjMnBrcWRkNQ&hl=en
Addressed Krupa's comment in the doc.

For error messaging when submission fails or required field is empty, let's reuse code from the worker mgmt form and follow the same user flow and functionality, whatever that may be.

When submitting with required field(s) empty, page refresh should highlight each field with red border and have error message above to the effect of:

"We need answers here. This field cannot be empty"
Sam,
I checked out the form in your dev box and it looks really good. I dig the +/- buttons.

Still need to add descriptions/messaging above the fields on the form to give the user context and instructions, for example:

Overview *
Briefly describe the background, goals and objectives for this project.

Use this doc as reference:
https://docs.google.com/Doc?docid=0AQf0FGHoPL05ZGc3bXpnNHNfMTNjMnBrcWRkNQ&hl=en

As per our email discussion, this form with trigger a top level bugzilla. no dependency bugs.
form is updated
https://webtools.wiffu.com/webdev/project_init

malexis, stage bugzilla has been refreshed so use your current bugzilla credentials to login to https://webtools.wiffu.com (not the credentials I gave you before)

I'll now move on to implementing the actual creation of the bug.
Status: NEW → ASSIGNED
Two small copy tweaks needed in the form. In the first field it should read "Project Name" and in the team members section, let's change "marketing" to "engagement"

The functionality looks good and I'm able to sumbit bugs in staging. We do need this on the intranet by Monday's all hands so I can demo it using the live URL.
I updated that copy
http://webtools.wiffu.com/webdev/project_init
and cc'd you on the bug for IT

sam
Attached image Error message
I got this error message when I tried to log in without giving a password.
Minor nits:

* Web Dev should be "Webdev", iirc (https://wiki.mozilla.org/Webdev)
* Logout should be "Log out"

Suggestion:

* Might be outside of the scope of this bug, but it'd be cool if we could have default mappings of contact to their areas
- empty password and/or username : fixed
- Logout should be "Log out" : fixed
- Web Dev should be "Webdev" : fixed

http://webtools.wiffu.com



can you expand on "default mappings of contact to their areas"  in this bug or email,  not sure I understand.

thx,
sam
(In reply to comment #14)
> can you expand on "default mappings of contact to their areas"  in this bug or
> email,  not sure I understand.

Sure; simply meant that, for l10n, WebQA, etc., we had default assignees, in the case where the project-initiator didn't know whom to CC, but that also comes with a small amount of administration overhead, and (hopefully!) project initiators should know who's working on their project, anyway.
I'm with you know.

That is doable, would entail building a mini admin section to to app , unless "who is default assignee to what" is stored somewhere else ?

malexis, do we want to start a 'feature request' list somewhere? or just open bugs? Not sure what the common practice is here at mozilla.

sam
I think it's a good feature to have, but let's consider default mapping of contacts out of scope and we can implement that in the next iteration. I'll keep a list of requirements for phase 2.
Sam, 
Tested the form on staging and looks good. 

https://intranet.mozilla.org/stage-webtools/webdev/project_init

I think we need to add some messaging to confirm to the user successfully submits. Maybe when page refreshes just highlight in green above the form where error message goes and say:

"Success! A bugzilla ticket has been created for this project and the Web dev will be in touch."

otherwise looks good.
Blocks: 581233
I'll add the specified text
"Success! A bugzilla ticket has been created for this project and the Web dev
will be in touch."

to the success message,  closing this out
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Sam, I was way off on the Product and Component for the form. Need to change them to:

Product: Mozilla.org

Component: WebDev
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
closing,  opened new bug for new issue
Bug 584548
Status: REOPENED → RESOLVED
Closed: 14 years ago14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: