FogBugz Technical Support

A forum for technical support discussion related to Fogbugz.
The current FogBugz Knowledge Base can be found at http://help.fogcreek.com/fogbugz.

Posts by Fog Creek Employees are marked:

Documentation
Release Notes
Network Status

API: Case Changes as Another User

It would be a nice (and admittedly, potentially dangerous) feature if the API, when used by an administrator, could be used to submit updates to cases "as" specified users.

For example -- I might have a reason to use the API to say "Edited by Joe Blow: Man, this is a really tough problem!" ... even when I am not Joe Blow, but an admin user.

Perhaps this could be an even more special type of account ... not an administrator account, but a "superuser" account.

I'd happily pay for another type of user per month (I'm using On Demand) that would be allowed to make these kinds of changes via the API. Even if the resulting edit was flagged with:

Edited by Joe Blow (via apiadmin user) ...

I took a look at the BugzScout approach, and found that it really wasn't flexible enough for what I wanted to do here. (What I want to do: add case events via Subversion commits, with the "Edited by" reflecting the developer who made the commit, not the user account accessing the API.)

... any possibility?

Thanks,
Clay
Clay Loveless Send private email
Thursday, December 6, 2007
 
 
I don't think there's a way to do that currently, and I'm not sure there's enough situations to justify creating that feature.

However, I do think that Subversion commits should create a BugEvent, and I've added your vote to the open case we have for that feature request.
Eric Nehrlich Send private email
Thursday, December 6, 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 Scheduling.