addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscontroller-playcredit-cardcrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobe--smallglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1launch-new-window--smalllight-bulblinklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonprintShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Managing Multiple Clients - Features Requests, Bugs, etc

From: Andrew
Sent on: Sunday, September 9, 2007 3:11 PM
Hey guys,

I'd like to get some thoughts from the group on something. I'm
currently receiving from clients - feature requests, bugs, etc -  via
email. What I need is a system that will keep one clients information
separate from another, yet i still receive everything organized by
client, then type. I want the client to do the data entry. I want it
to be secure, but usable by all necessary parties.

QUESTION: How do you all manage all the requests, bugs, etc for
multiple clients? Do you set up your system in a secret URL for all
your clients to access? Have you encountered any resistance from
clients to using such a system?

BACKGROUND: I've used Bugzilla to track bugs while working for a
single company, and it worked  pretty well. This was always behind the
company firewall. I could see the bugs assigned to me and work down
the list. Someone else inside my organization would enter the bugs,
and assign them to me.

Andrew Woods

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy