FogBugz Technical Support

A forum for technical support discussion related to Fogbugz.
A more vibrant community can be found at http://fogbugz.stackexchange.com.

Posts by Fog Creek Employees are marked:

FogBugz Q&A
Documentation
Release Notes
Network Status

How do I create a case for someone else?

I have some users who refuse to use FogBugz to enter their bugs, but want to be notified the second their issues are fixed!

So is there any way that I can open a bug as if I were another person, so that when it's resolved that person will get the email?  Or is there a better way to do this?

Thanks
Paul S
Wednesday, February 28, 2007
 
 
Yup!  When they come over to say when is my bug going to be fixed tell them it's not in FogBugz so you can't fix it.

OR set up an email address for them like bugs@company.com that goes into FogBugz and then when its finished assign it to the account you created it for them so they get an email notification (of course then they'll ask you for their password :)

From: http://www.joelonsoftware.com/articles/fog0000000332.html

"For example, suppose nobody on your team can be persuaded to use a bug database. Don't let it bother you. Just keep your own. Enter bugs that you find in your own code. If you find a bug that somebody else really should fix, assign the bug to them using the bug database. If you have good bug tracking software, this will send them an email. But now, you can keep sending them emails if they don't fix the bug. Eventually, they'll see the value of bug tracking and start to use the system as it was intended. If the QA team refuses to input bugs to the bug tracking system, simply refuse to listen to bug reports through any other channel. About the three-thousdandth time that you say to people, "listen, I'd love to fix that, but I'm going to forget. Can you enter a bug in the system?" they'll start using the database."
Michael H. Pryor Send private email
Wednesday, February 28, 2007
 
 
There are so many situations where you can't simply tell them to enter it themselves, that it's worth having the ability to be able to enter it for them.

Sometimes it's just better to appear to be more helpful, rather than telling people to bugger off and enter it themselves.

Sometimes they're ringing up from out of the office, other times it might be a list of bugs/features from a meeting/review that you know the one person is interesting in seeing resolved, but another person is the one who minuted the meeting and is in charge of entering issues into FogBugz.

It would be fantastic if there was a drop down box where you could select who opened the case. There'd need to be permissions for this of course.
Ray
Wednesday, February 28, 2007
 
 
>>>
It would be fantastic if there was a drop down box where you could select who opened the case. There'd need to be permissions for this of course.
<<<

YES!

We often want this. For example, I will be at the desk of one of the devs, and we will open a case together, at his desk, assigned to him.

Now I want it auto-assigned to me when he resolves it... but that won't happen, because we opened the bug at his desk, logged in as him.


I have often pined for exactly this feature.
Sam Jones
Thursday, March 01, 2007
 
 
Advice in other parts of the documentation suggest you should enter the bug, assign the case to the other user so they get a notification email with a URL, then assign it to yourself. You could also send a reminder with the "subscribe" link in it.

I completely understand the need, however, for two user fields: (1) the currently assigned to field and (2) an "owned by" or "stakeholder" field.

Lots of people have called for additional ways to "subscribe" to cases and views, so you're no where near alone, but this sounds like Joel's touchy subject of notification and human engineering: i.e., why can't we get email alerts to posts in this forum?
flipdoubt Send private email
Monday, March 05, 2007
 
 

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
 
Powered by FogBugz Bug Tracking and Evidence-Based Sheduling.