Deleting projects?
7 answers
bmiller wrote:
Yesterday there was a similar post about changing the process template.
Quick answer is it is not supported and some manual work should be done.
Check "Is there any way to switch Eclipse Way to" subject in same forum.
Project Areas can't be deleted/removed from the repository. They can be
archived and configuring your UI filters it won't be seen and won't be
able to use it. If you want to reuse exactly the same name, you should
rename the archived Project Area.
Hope this helps,
Chemi.
Hello gurus,
I created a project and made the poor choice of selecting Simple Team
Process (I really miss the Eclipse Way process template) which has
inadequate control of permissions. Is it possible to either change
the process template or delete the project and begin again?
Cheers
-Bryan
Yesterday there was a similar post about changing the process template.
Quick answer is it is not supported and some manual work should be done.
Check "Is there any way to switch Eclipse Way to" subject in same forum.
Project Areas can't be deleted/removed from the repository. They can be
archived and configuring your UI filters it won't be seen and won't be
able to use it. If you want to reuse exactly the same name, you should
rename the archived Project Area.
Hope this helps,
Chemi.
bmiller wrote:
Hello gurus,
I created a project and made the poor choice of selecting Simple Team
Process (I really miss the Eclipse Way process template) which has
inadequate control of permissions. Is it possible to either change
the process template or delete the project and begin again?
Cheers
-Bryan
Yesterday there was a similar post about changing the process template.
Quick answer is it is not supported and some manual work should be done.
Check "Is there any way to switch Eclipse Way to" subject in same forum.
Project Areas can't be deleted/removed from the repository. They can be
archived and configuring your UI filters it won't be seen and won't be
able to use it. If you want to reuse exactly the same name, you should
rename the archived Project Area.
Hope this helps,
Chemi.
I don't need to switch to Eclipse Way necessarily. I just need a process template that allows my team to have full control and hundreds of contributors to only be allowed to submit work items and discuss them.
You can do some pretty simple configuration to get what you want.
Create two roles, for example contributor and developer.
When configuring permissions for each in the Process Configuration tab of the project/team/template editor, you can right click the role and use "Grant All Actions" and "Revoke All Actions" to quickly get things so developer can do everything and contributor can do very little.
Hope that helps,
Ryan
Jazz Team
Create two roles, for example contributor and developer.
When configuring permissions for each in the Process Configuration tab of the project/team/template editor, you can right click the role and use "Grant All Actions" and "Revoke All Actions" to quickly get things so developer can do everything and contributor can do very little.
Hope that helps,
Ryan
Jazz Team
You can do some pretty simple configuration to get what you want.
Create two roles, for example contributor and developer.
When configuring permissions for each in the Process Configuration tab of the project/team/template editor, you can right click the role and use "Grant All Actions" and "Revoke All Actions" to quickly get things so developer can do everything and contributor can do very little.
Hope that helps,
Ryan
Jazz Team
Thanks Ryan. Those are both very helpful replies.
-Bryan
You can do some pretty simple configuration to get what you want.
Create two roles, for example contributor and developer.
When configuring permissions for each in the Process Configuration tab of the project/team/template editor, you can right click the role and use "Grant All Actions" and "Revoke All Actions" to quickly get things so developer can do everything and contributor can do very little.
Hope that helps,
Ryan
Jazz Team
I'd like to make the following distinctions:
1) developer - can do most everything
2) contributor - a bit like a guest developer
3) customer - can create work items, contribute to discussions, etc.
Is this level of granularity possible with the simple team process model?
I think you can configure what you want. Create the 3 roles, then poke around in the permissions in the project/team editor in eclipse and see if the permissions are granular enough to achieve what you describe. There won't be a high level checkbox for "contribute to discussions", but the work item permissions are quite granular, so you can permit/deny a role to make comments for example. In the permissions tree expand Work Items / Save Work Item / Modify the work item / Add a comment.
---
Ryan Manwiller
Jazz Team
---
Ryan Manwiller
Jazz Team