Home → Suggestions →

An easier way to make an issue default to public (or batch change the status of issues to public)

• Edit

Aral Balkan

11 Sep, 2009 11:09 AM

I'm going to be receiving quite a number of issues via email. All of these default to private in the current system. This is cool for generic feedback where I can't be sure if there's sensitive info in the issue but for this particular type of feedback, I know that there won't be any since my app is generating it.

For these issues, it would save me a lot of manual labor if I could set the tickets as public by default. (So a an email address/category-level setting that results in emails sent to that category/email being marked public as default instead of private.)

Barring that, it would be great if I could batch select a number of issues and set them to public.

As is, I have to go into each issue and make it public which is taking lots of clicks and time (and will take more once the app is in alpha) :)

Thanks! :)

1. 1 Posted by rick on 11 Sep, 2009 04:45 PM

   

   I'll add a bulk option for sure.
   

   As for incoming email -- I want to be careful that we don't make this system too complex by overloading it with options. There are at least 4 or 5 ways we could conceive of configuring Categories with how they handle issues.

   • Edit

2. 2 Posted by delete_johan on 24 Apr, 2010 11:18 PM

   

   I would also very much have the option of making email ticket public on default. It would be easy enough to include in the response a link that says

   This support request is availabel at: link_to_discussion
   As a general rule, we like to keep questions and discussions about potential problems open. If this is a private issue, please mark this discussion private by clicking on this link: link_to_make_private

   • Edit

3. 3 Posted by bradley on 20 Jul, 2010 03:04 PM

   

   +1 for having option to make incoming emails default to public. We're trying to use tender as an internal question/answer repository for our staff. They're used to submitting questions to listservs but this obviously has better visibility and tracking. The benefit of it being public is that anyone in our organization can answer the question without us having to make everyone in the org a support agent.

   • Edit

4. 4 Posted by bradley on 20 Jul, 2010 03:31 PM

   

   Another alternative would be to simply add an option to Filters to allow you to make the discussion public.

   • Edit

5. 5 Posted by bradley on 20 Jul, 2010 03:35 PM

   

   We just found an API call to allow us to update the public/private status programmatically (see "Discussion Actions")

   • Edit

6. brandi closed this discussion on 23 Dec, 2010 06:16 PM.