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!

[Uladzislau Samuseu · Accepted solution]

Hi there! Support response:



I'll post the solution after if somebody need.

[Jack Brickey]

Thanks for the update

[Johann Riedel]

Thanks - we'll stay interested :)

[Johann Riedel]

Hi @Uladzislau Samuseu - the issue seems to be resolved. 

[Uladzislau Samuseu]

@Johann Riedel Yes mate, we won!

[Jack Brickey]

So it was a regression that was fixed?

[Uladzislau Samuseu]

@Jack Brickey it's true

[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.

And I'm of your opinion - the admin permission should only be needed for setting a default restriction on an issue type.

[Uladzislau Samuseu]

Hi, @Johann Riedel 

We are negotiating with support at the moment. As soon as I receive an answer I will write the solution here.

[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.

[Uladzislau Samuseu]

Hi @Dexter de Vera ,

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

[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.

[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.

[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]

Thanks for participation anyway!

[Jack Brickey]

I remain intrigued. I found this post from February of 2023 which illustrates the same wording on this permission. So, while the wording hasn't changed, may be something in the behavior has.

Where-is-the-"Restrict-any-issue" permission 

[Uladzislau Samuseu]

I believe that the error is in the behavior. I also sure that the wording was changed exactly last week in my case. But thanks for the info.

[John Funk]

So, you are using ScriptRunner Behaviours app?

[Uladzislau Samuseu]

No, should I?

[John Funk]

No, I just got confused when I saw you mentioned behavior. 

[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]

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

[Uladzislau Samuseu]

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

[Ste Wright]

Hi @Uladzislau Samuseu 

Thanks for confirming. I was referencing this article (albeit from 2020) which states...

Please note, to set issue restrictions for issues in a next-gen project:

• You must either be on the Jira Standard or Premium license plans.

• You are assigned to a role that has the SET_ISSUE_SECURITY permission. Admins and users assigned to the Member role are given this permission by default. Learn more on how to grant permissions to roles in next-gen.

...which seems to suggest Members should be able to do it also?

Ste

[Uladzislau Samuseu]

Right, it were so till the last week, but now it's not, either you are member or have any other role with this checkbox

[Ste Wright]

Hi @Uladzislau Samuseu 

This might be a bug - but I couldn't find one matching this issue in the bug list.

I'd report this to Atlassian Support 

Let us know what they say :)

Ste

[Uladzislau Samuseu]

I'll try, thanks a lot!

[Jack Brickey]

If you do report and get a response back, please update the post here for all of us interested in the outcome.