We use JIRA/Grasshopper to manage our consulting/development projects and want to know if there is a way we can have a hierarchy of our customers and the stories/tasks they want us to work on. We want to give access to our customers so they can see their stories and
so we can see stories for all the customers (ie: swimlanes for each customer on our khanbahn board).
Is there some way this can be accomplished by adding users and using "Groups"?
This is what I did in case anyone gets as lost as I was. It's probably not best solution but is working right now in restricting Customers to only one project and not causing too much setup overhead:
Create new projects for each customer.
Create a Customer Group for each customer.
Create Customer users and add them to this group.
Optionally, create a system role called “Customers” and apply it to all Customers groups. It makes understanding permission sets clearer.
For each project, set the Customer Group as the “Users” project role and “Customers” project role. Also include the “users” project group in the “Users” project role, depending on if your permission sets reference the “Users” project role.
Remove the Customer users from the “users” group. The reason for this is that by default for new projects the “users” group is set as the “Users” role in project. If Customers are in this group then they will can see any project.
Assign Customer Group to the Jira Global permission “Jira Users”. Only the “users” group has this permission and now the Customers need this or else they won’t be able to see anything in Jira or log out of Jira once they get in.
Create a Customer-access permission scheme to each project. Allow Customers to browse projects and create edit issues. They should only see the projects for which they are in the Customers/Users project role, however.
Add conditions to Greenhopper transitions to prevent them from moving Issues in the boards.
In current Greenhopper you are not able to restrict user groups to manage which user can view those specifield issues. However, you can set a issue serutiry level for each issue which only allow certain users to be able to view that particular issues.
Here is a doc might helpful on how to Configuring Issue level Security:
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs