Permission issue

[nika gabadze]

Hello , I've created security schemes, and now i have issue to see some task , for example someone created task in my organization and use security scheme to not having the access other users , unfortunately he excluded himself form that task and now now one can see that task even the org admins , there are added in the every security scheme , 

do you have any idea how remove security scheme or get the access on that task ?

[Morgan DUBUISSON · Accepted solution]

Hello,

To resolve the issue with the security scheme, you can try accessing the Permission Helper tool. It can be found at the following URL:

https://XXX.atlassian.net/secure/admin/PermissionHelperAdmin.jspa

This tool should help you identify any permission or security scheme issues related to the task in question. Once you locate the problem, you can adjust the security settings accordingly to regain access.

Let me know if you need further assistance!

[nika gabadze]

Hello , thanks for the info , im on it and ill let you know 

[nika gabadze]

thank you so much , i have found the task and everything , but when i try to edit the permission im getting this err message : 

[nika gabadze]

solved it thank you so much

[nika gabadze]

it was really helpful 

[Morgan DUBUISSON]

With pleasure, @nika gabadze

If this request is resolved, I invite you to mark it as resolved.

Have a great day!

[nika gabadze]

okey sure , 


you too!

[Lucas Modzelewski _Lumo_]

Site note: info on the page is the same if you don't have access or if issue doesn't exist 
(to speed up checks you can use /rest/api/3/issue/{ISSUE_KEY} )

To check if it was the last issue created in project you can check if next issue key is higher.

-- 

I've run a quick checked and editing correct security lvl I was able to regain access to the issue, so make sure you are editing correct (or all security lvls, to find the right one to make changes)

[Fazila Ashraf]

Hi @nika gabadze 

Welcome to community!

Please try the approach to include reporter in the security level as suggested by Fabio to workaround now.

If you share what type of approach you have used to configure the security levels, could advise you on the best practise to avoid such issues 

[nika gabadze]

Hey @Fazila Ashraf  the user has used this restriction 

[Fabio Racobaldo _Herzum_]

Hi @nika gabadze and welcome,

try to set Reporter in the security level so that each user that create a ticket has, by default, permission to see it.

Hope this helps,

Fabio

[nika gabadze]

Hello @Fabio Racobaldo _Herzum_  thanks for your response i have already tried but unfortunately facing the same issue , this is how how my security scheme looks like : 

• Project Role (Administrators) (Delete)
• Project Role (Service Desk Team) (Delete)
• Reporter (Delete)
• Project Role (atlassian-addons-project-access) (Delete)
• Current assignee (Delete)
• User custom field value (Collaborators) (Delete)
• User custom field value (Approvers) (Delete) 
• Single user (nika gabadze)

[Fabio Racobaldo _Herzum_]

Hello @nika gabadze ,

it's weird. Are you sure that ticket has this Security Level? If so, all those users should be able to see it. My thought is that ticket has a different security level with different permissions.

As workaround try to set Security Scheme to none in your project so that all users with browse permission can see tickets so that you can check that specific ticket configuration.

Hope this helps,

Fabio 

[nika gabadze]

Project type is software , IDK because i Added myself in very security scheme which i have at this moment

[nika gabadze]

sorry , user used this restriction, and first he applied this for administrator role and after that he remove administrator role 
 

[nika gabadze]

how does this restriction works ? , i don't get it 

[Fabio Racobaldo _Herzum_]

did u solve?

[nika gabadze]

yes Fabio and thanks for you attention