0

How can we prevent public access to the {ticketurl} or {ticket} without restricting the correspondent's access?

Some of our correspondents are passing sensitive information to us through FogBugz cases. They are submitting links to other cases in our support forums, exposing all of their cases to the public. They are clearly not aware that they might expose their sensitive information this way.

We're trying to educate our users to keep their {ticketurl} private, but we'd like to enforce this somehow.

I see several ways this can be solved:

  1. Removing the correspondent's case listing at the bottom of the public {ticketurl}-page, but that would the correspondents' sense of their history.
  2. Coding a gate keeping page, where the correspondent have to paste his {ticket}, but that still does not prevent them from posting the {ticket} publicly and still require some education of our correspondents.
  3. Same as 2. just with a more aggressive authentication system that require a correspondent to log in.

Is there a way to manage this situation with an existing FogBugz feature or a plugin?

flag

1 Answer

1

If the url has 8 random characters the end it will show all the other corresponding tickets. If you chop off 4 of those characters, the url will now only show you that particular case (and no other cases).

link|flag
This is good to know. However, I would like to know if there is a built-in way to accomplish this. Currently we're using the {ticketurl} placeholder to provide the submitter with a tracking URL. Is there an equivalent for this omitting the last four characters or do we need to chop them off manually? – Nicolaj Schweitz Jan 7 2010 at 9:19
I mean manually as in running it through a non FogBugz application. The auto replies need only to have the url to the particular case. – Nicolaj Schweitz Jan 13 2010 at 11:02

Your Answer

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