Anyone know of a way to limit customer views? I have a number of different companies collaborating on projects. I need each company to have limited read access so they can only see the issues assigned to their project. Any info would be appreciated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've actually done this, but it doesn't seem to prevent that user from seeing the other issues in the system. All that user has to do is change the filter under the "View Issues" page. Am I missing something?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The users only see issues on projects they have access to.
Make sure that in User Admin you select all projects a user can have access to. Then all issues on those projects should be visible to him/her.
If I'm mistaken, please let me know.
Thanks.
philip
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you click on View Users, all the users are shown. I would prefer if only the users associated with a given project are shown. On the other hand, if one user logs in, he has access to all of his projects.
So maybe it is more like a reverse lookup:
1) check to which project the current user belongs
2) show only users that belong to one of these projects.
If I think about it now, there are more important things to have than this. Still, it would be a nice feature for certain applications.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You mean in any drop-down lists that allow you to pick a user? The answer is no, not as of now.
But if you could spend like 5 minutes to give me description of what you're interested in, I would surely consider implementing something in some future version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just verified that a user can see any issues in the system simply by modifying the filters. I did this after installing the CVS version just in case.
Under "User Admin" I created a new user. I checked the box next to the project that he should have access to.
Then I log out and log back in as the new user. Under "View Issues" I select Modify. I change the filter properties for "Assigned To" to (Anybody). Then Save&Go to display every issue on the site under any project.
Everything else works fine, the best project app I've used yet. Any thoughts?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
CVS has a version that would limit the list of issues to projects that the user has access to (even when they select "All").
Give it a few hours to fully propagate to mirrors and you can check it out and let me know if it does the trick for you.
It probably should be more extensive that this, but I'll update them as I come across. If you feel this applies to any other area, please feel free to mention it here. The more eyes the better.
Thanks again!
philip
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
At my company we use RT (http://www.bestpractical.com/rt/) for this kind of heavyweight issue tracking. I find projectbench much better for lightweight project todo lists. RT has all the permission stuff you need and more, but of course it's a lot more work to set up and learn and administer, and it's slower too.
RT also doesn't have the concepts of roadmaps projct versions, which projectbench does.
-- Gary
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My experience, limited as it is, showed me that with small companies there's usually an intrepid developer that sets up some sort of issue tracking system.
As such, there will be an ad-hoc rather than a dedicated administrator. It is my intention to make this pseudo-administrator's life as easy as possible. With a detailed permission system, thing tend to get really high maintenancce. I don't want this pseudo-admin to go RTFM to figure out what some cryptic permission means and whether he needs it or not.
Even if that makes PB unsuitable for large companies with control-freak management...
That being said, I am always willing to implement (security) suggestions as long as they make everybody's life easier and keep with the "doctrine" of PB: friendly project management.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anyone know of a way to limit customer views? I have a number of different companies collaborating on projects. I need each company to have limited read access so they can only see the issues assigned to their project. Any info would be appreciated.
You could create one user account for each customer/company and give them access only to their respective projects.
That's what I've done in the past in a similar case.
I've actually done this, but it doesn't seem to prevent that user from seeing the other issues in the system. All that user has to do is change the filter under the "View Issues" page. Am I missing something?
The users only see issues on projects they have access to.
Make sure that in User Admin you select all projects a user can have access to. Then all issues on those projects should be visible to him/her.
If I'm mistaken, please let me know.
Thanks.
philip
This is along the same line:
Is there a way that a user only sees other users that belong to the same project?
You mean in any drop-down lists that allow you to pick a user?
If you click on View Users, all the users are shown. I would prefer if only the users associated with a given project are shown. On the other hand, if one user logs in, he has access to all of his projects.
So maybe it is more like a reverse lookup:
1) check to which project the current user belongs
2) show only users that belong to one of these projects.
If I think about it now, there are more important things to have than this. Still, it would be a nice feature for certain applications.
You mean in any drop-down lists that allow you to pick a user? The answer is no, not as of now.
But if you could spend like 5 minutes to give me description of what you're interested in, I would surely consider implementing something in some future version.
I just verified that a user can see any issues in the system simply by modifying the filters. I did this after installing the CVS version just in case.
Under "User Admin" I created a new user. I checked the box next to the project that he should have access to.
Then I log out and log back in as the new user. Under "View Issues" I select Modify. I change the filter properties for "Assigned To" to (Anybody). Then Save&Go to display every issue on the site under any project.
Everything else works fine, the best project app I've used yet. Any thoughts?
You're absolutely right. D'oh :))
I will file this under bugs. Thanks a lot.
CVS has a version that would limit the list of issues to projects that the user has access to (even when they select "All").
Give it a few hours to fully propagate to mirrors and you can check it out and let me know if it does the trick for you.
It probably should be more extensive that this, but I'll update them as I come across. If you feel this applies to any other area, please feel free to mention it here. The more eyes the better.
Thanks again!
philip
At my company we use RT (http://www.bestpractical.com/rt/) for this kind of heavyweight issue tracking. I find projectbench much better for lightweight project todo lists. RT has all the permission stuff you need and more, but of course it's a lot more work to set up and learn and administer, and it's slower too.
RT also doesn't have the concepts of roadmaps projct versions, which projectbench does.
-- Gary
My experience, limited as it is, showed me that with small companies there's usually an intrepid developer that sets up some sort of issue tracking system.
As such, there will be an ad-hoc rather than a dedicated administrator. It is my intention to make this pseudo-administrator's life as easy as possible. With a detailed permission system, thing tend to get really high maintenancce. I don't want this pseudo-admin to go RTFM to figure out what some cryptic permission means and whether he needs it or not.
Even if that makes PB unsuitable for large companies with control-freak management...
That being said, I am always willing to implement (security) suggestions as long as they make everybody's life easier and keep with the "doctrine" of PB: friendly project management.