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; } } }

Why users now can't restrict issues?

Uladzislau Samuseu

Even if users in my team-managed project have specific permissions to restrict issues they can't do that, cuz they have to be as admin too. So, how i have to use this option in order to enable users to restrict issues how it was before? Ofc I cant give them all admin role.

Thanks for your support!

Accepted answers

Uladzislau Samuseu

Hi there! Support response:

I'll post the solution after if somebody need.

All comments

Ste Wright

Hi @Uladzislau Samuseu

Have you had a non-admin user try that?

I'm reading it as you need to be an admin to set default restrictions, but non-admin users can limit access to issues normally.

Or is this what you're referring to have tested in the error screenshot?

Ste

Uladzislau Samuseu

Hi @Ste Wright

Non-admin users can't use restriction at all, even if they have "Restrict any issue" checkbox in their role. As far as I understand correctly, only admin now can restrict issue due creating and after that.

I think that's not work correctly, because now i can't give users with non-admin roles opportunity to restrict any issues at all, due creating or after that.

P.S. The screenshot with an error was made by non-admin user.

Jack Brickey

Hi @Uladzislau Samuseu , you mentioned "how it was before". To the best of my knowledge this access permission has not changed since introduced. However maybe I am misunderstanding a question.

Jack Brickey

The ability to restrict is a project admin only operation as stated.

Uladzislau Samuseu

Greetings @Jack Brickey !

A week before it was an opportunity to restrict any issues even by users with non-admin roles. That's why i wrote so.

Uladzislau Samuseu

It's illogical now, cuz if i have admin role i am able to restrict any issues already even without this checkbox

Dexter de Vera

Hi @Uladzislau Samuseu ,

Have you tried to do the changes in the ticket view itself not in search view. Can you try to click the ticket ID. Then after you directed to the ticket itself you may do the update of security.

Jack Brickey

That is interesting. I had not experienced that prior but admittedly I do not use TMP much.. Maybe something rolled out to change the behavior. Might be worth contacting Support to inquire.

Uladzislau Samuseu

Hi @Dexter de Vera ,

Thanks for your suppose, but restrictions not work for non-admin roles in any views.

Uladzislau Samuseu

Thanks for participation anyway!

Johann Riedel

Hi Uladzislau,

we've encountered the exact same problem last week.

So I'm really looking forward to hearing what you were able to find out.

At least I can confirm that this is indeed an issue right now.

Currently restricting an issue is linked to the "administer project" permission, what makes no sense to me as members should be (and were, if I recall correctly) able to do this, as well.