No, project permissions are done at that project level. A user can either see all the issues in the project, or they see none of it.
The only lower layer is "issue security". This lets you set a "level" on each individual issue which can restrict its visibility to a sub-set of people with project permissions.
It's done on an issue by issue basis with a single "security level" field, not by component or issue type or anything else. This is why Joe mentions scripting - you could write a script that does things like "if component = CRM, set security level X"
interested in exactrly the same issue resolution:
all tasks with [Component] = "Import"
_visible_ only to [User group] = "Import_department"
if anyone could help HOW TO set this up - in coding or post function or whatever - that can actually DO IT - would kindly appreciate. (freelance coders also interest) - or any suggestions where to find the solution...
thank you in advance
First, set up a issue security scheme that does what you need (one level for "import", with a rule "only group import_department")
Second, use the ScriptRunner built-in script (see https://scriptrunner.adaptavist.com/latest/jira/builtin-scripts.html#_set_issue_security ). That wasn't built in until recently.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
A picture tells a thousand words. And agility boards have just released their latest feature: cover images on issues – so now your board can tell a story at first glance. Upload attachmen...
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