Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

issue level security : can UserType-A view secured issues but only UserType-B edit the security?

I'm new to issue level security, but I've got it working for the first time just now - yay!

I have two issue security levels:

  • 'any logged in user' and this is set to any logged in user as you can imagine :)
  • 'XYZ personnel only' and this is set to a Project Role 'XYZ personnel'

It seems to work:

  • issues set to 'XYZ personnel only':
    • cannot be viewed by a 'normal' user
    • can be viewed by users with the Project Role 'XYZ personnel'
    • So far so good...

But is it possible to configure issue level security so that:

  • UserType-A can view issues set to 'XYZ personnel only' but cannot change the issue's security level
  • UserType-B (e.g. Project Role 'Administrators') can both view the issues set to 'XYZ personnel only' and edit the security level on the issue

This possible?

 

1 answer

1 accepted

2 votes
Answer accepted
Dave Mathijs
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jul 20, 2022

Hi @Arnold , yes this is possible based on permissions.

When a user is part of the security level, that user can see the issue.

All other 'operations' are managed by permissions in the permission scheme associated with the project.

thanks @Dave Mathijs

Ah yeah - got it.

Now my testuser can view secured issues but cannot edit the security level (but can edit other fields as usual)

It's working now :)

Thanks!

For others who are interested in how I got it to work:

Project Admin > Permissions > Set Issue Security = Project Role 'Administrators'

Issue Level Security is as in the original question:  security level = 'XYZ personnel only' can be seen by users with Project Role 'XYZ personnel'

Project Admins can edit an issue's security level

'XYZ personnel' can view a secured issue but cannot edit its security level (the field doesn't appear in the 'Edit Issue' screen).

:)

Like # people like this

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events