FogBugz Technical Support

A forum for technical support discussion related to Fogbugz.
The current FogBugz Knowledge Base can be found at

Posts by Fog Creek Employees are marked:

Release Notes
Network Status

Different scopes for public submissions

In our company we have project groups who provide components for other project groups, which means that the latter developers that use the components need to be able to file cases for the projects that develop those components. At the same time we don't want every developer who just uses some component to have write access to the component's project. So what we do is that we allow public submissions on the component projects, as currently our FogBugz web site is only accessible from inside our company network.

There are two problems with that, though:

1) A developer which wants to do such a public submission needs to log out from FogBugz to be able to do so, because when logged in the New Case dialog shows only the projects for which the user has write access. This can be quite annoying.

2) In the near future we want to allow external customers to be able to publicly submit cases, but of course we don't want them to see (or submit cases to) our internal "component" projects. Which means that either we can't do this or we have to stop using the public submissions feature for our internal purposes.

So, what would be useful is to have two levels of "public submissions", one for external users (external customers; community users) and one for normal FogBugz users which don't have write access to the project.
Niklas Matthies Send private email
Tuesday, October 28, 2008
Why not have FogBugz poll a mailbox and have people submit their submissions via email to a special mail account?  Or you could even make a html form page they go to and fill out that just sends the message on the backend?
Michael H. Pryor Send private email
Tuesday, October 28, 2008
Being able to track the cases via the web interface (using ticket URLs) is a requirement for us. As far as I can see this entails making the "public submission" interface public.
Niklas Matthies Send private email
Tuesday, October 28, 2008
No, I don't believe the project has to be public in order for the ticketurl to work.

The autoreply can send them back the ticketurl so they can track their case (remember, the public view of a case ONLY shows the public email events they have already received in their inbox, not any private events).
Michael H. Pryor Send private email
Tuesday, October 28, 2008
Well, as I explained, we have projects that already are public for our internal purposes. I guess we could make the external customer projects public instead and let our internal "customer" users use e-mail only or a different web form as you sugget. (The latter likely won't happen, and would be confusing for a normal FB user to have to go to a non-BF page.)

Anyway, all of this is a hackish workaround at best. Since with FB7 fogcreek is going for more flexibility, please add what I outlined in the first message as a feature request:

1) Better support for FB users that are part of different projects being in the role of "customers" or "community users" of each other (e.g. project A uses project B, so project A is a customer of project B).

2) More fine-grained permissions for "public" submissions. This is similar to how wiki access can already be configured separately for community users and for anonymous users. In that veign, for submissions from users without project write access, provide different permissions for normal users, community users and anonymous users.

3) [while I'm at it] For anonymous users, remember their e-mail address and project/area/version of their last bug submission. (Possibly as an option, using a "remember my settings" checkbox.)
Niklas Matthies Send private email
Tuesday, October 28, 2008
I passed along your message to the team to consider your comments for a future version of FogBugz.  Sorry I forgot to update this topic!  My apologies...
Michael H. Pryor Send private email
Thursday, October 30, 2008

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.