6

Do you support the notion of a no-charge automation user account for FogBugz On Demand? Note that this is different from the Virtual User concept. We would be interested in employing an automation account to inject cases into FogBugz automatically via API when an error occurs on our web site. Here is how Perforce handles this concept:

"A 'background user' is a Perforce user account that is used solely for automated tasks, such as triggers and daemons. Perforce customers with current licenses can request an additional user added to their license file, free of charge. Contact Perforce support for more information.

( From http://kb.perforce.com/article/723/triggers-and-passwords )

With a FogBugz automation user account, we would not have to code a human user's credentials into our web back end, and a user's stats wouldn't be polluted by an automated process that opens cases under his or her name.

Proposed properties of the automation account:

  • It cannot log in to the UI
  • It does not show up in the "Assign to" list in the UI
  • Cases cannot be assigned to the automation user via API

Fog Creek Case FC2033236

flag

1 Answer

1

We have a feature request open for a limited XML-API only user. You can up-vote this question to show your support.

In the meantime, you can use an administrator user's XML API token to perform edits, and set ixPersonEditedBy to the ID of a Virtual User. The edits in FogBugz will show up as being performed by that user even though they are a non-license-using virtual one.

link|flag
The problem with this solution is that e-mail notifications are not sent to the user whose login credentials are being used, because FogBugz assumes that I know about anything that goes on from my login. This is normally a safe assumption, but in the case that I'm deliberately overriding ixPersonEditedBy, it isn't. – Drew Sep 12 at 9:04

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.