nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Restrict user

Marzi Goodarzian

" after creating issue, in "issue search screen" all user dont see the issues so that: user 1 and user 2 see bug issues and user3, user4 see task issue and...."

using issue security scheme, no one can not see other's issue.
this is different from my problem.
Is there solution?

thanks

Accepted answers

Bastian Stehmann

HI @Marzi Goodarzian,

just to get it right.

You want that one group of users can see only one issuetype and another group of users can see only another issue type?

All comments

Bastian Stehmann

HI @Marzi Goodarzian,

just to get it right.

You want that one group of users can see only one issuetype and another group of users can see only another issue type?

Marzi Goodarzian

Hi @Bastian Stehmann

Yes thats right.

Nic Brough -Adaptavist-

I would still say issue security is the right way to do this. Define an issue security level to match each issue type, and then have a post-function on the "create issue" transition that sets it by issue type (have a different workflow per type)

Bastian Stehmann

I think this should work using Issue Security.

If you create a Scheme with two security levels, called Bug and Task and for each level, you add the users that should be able to see the Bugs or Task, and assign that scheme to your project, you can use this security levels to restrict the users.

To have that working proberly, you must ensure that the users select the right security level when creating issues.

If you want the security level always set on creating an issue, you can use Script Runner for example to set the security level depending on the issue type.