Is there an free (or cheap) issue tracking software that allow you hide some issues to some member groups?

Question

I need a Issue Tracking System that allow me to share information on a selective manner.

I would be able to define these groups:

• supplier (my company)
• subcontractors
• customer

Then, I would be able to define three type of permissions for issues:

1. Issue that can be viewed only by supplier
2. Issue that can be viewed only by supplier and subcontractors
3. Issue that can be viewed by all (supplier, subcontractors, customer)

I tried redmine but I didn't find a way of hide some issues, they are always visible. There is an open issue and a patch for that but I not sure if it suit well for my situation. With this patch you need always to remember to make it private and there is only a level of permission: private or not. I need something more flexible.

EDIT:

I need a software that works on Fedora Linux.

Answer 1

FogBugz - http://www.fogcreek.com/FogBUGZ/

Free trial 25per user per month and you can setup different groups.

Answer 2

Jira security feature with issue and comment level security.
It is normally commercial licence.
But you could apply for free licence if you work for non profit organization (apply here) or with an open source (apply here) project.

Answer 3

It seems that the Bugzilla (one of the oldest large open-source bug tracking tools currently used for Mozilla projects (Thunderbird, Firefox, etc) might have the features you want, check out their Group security.

Answer 4

Flyspray is a free, uncomplicated bug-tracking system, supporting both global and project-level groups: i would give it a try.

Answer 5

If I recall correctly mantis does fit your requirements.

Answer 6

Mantisbt (free, Php) defines the notion of access level (that you can customize)

define( 'VIEWER', 10 ) // <= legacy 

custom_constant_inc.php

define( 'VIEWER_FOR_SUPPLIERS', 11 )
define( 'VIEWER_FOR_SUPPLIERS_AND_CONTRACTORS', 12 ) 
define( 'VIEWER_FOR_SUPPLIERS_FOR_ALL', 13 )

Caveat: some tweaking may be involved to associate those new access level with your bugs, in particular the definition of a custom field in the bug in order to classify it amongst your three "viewer" categories...

Note: you have also the possibility to limit the access of a user to the bugs he/she has opened.