I wan users to have access to see specific issues - the key grouping concept I would like to use is "components'. Thus, is there a way to assign users to components? Or even have groups or roles tied to compoenents and then users to the gorups or roles?
There is "component lead", but that isn't going to help you with this. You can't tie anything else to components, including security levels.
If you skipped components and used a dedicated group field instead, you could use that field in the security schemes to do this, but it's not going to work with components.
Nic, thanks. What we were trying to accomplish is to have different groups of people who can only see certain issues. Thus we were trying to use components, which won't work. Then we are looking at a different design. Lets say you have 4 groups - Inbound, Outbound, Process, Sales. you want inbound to only see issues for Inbound - this "Inbound" would have to be tied to something that can work thru security. Inbound can not see Outbound, Process can not see Inbound but can see Outbound. etc etc etc. You get the picture I am sure. We were thinking about using the addin for Service Desk and have a service desk for maybe each of the groups. do you have a suggested reading/link or opinon.
Yup, there's a trick here, but it does need a bit of code (although I use a script)
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
Planning and grooming sessions all come with their own sets of rules. Team members meet to estimate stories or other work items, all according to an agreed-upon process. And with every session comes ...
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