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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

I want to make filter to find security level but i dont want to write security level i need a security level of user who is using filter. Like currentUser(). What syntex i need.

The same with the memberOfGroup()

Level = ?

memberOfGroup(?)

membersOf("?")

1 answer

1 accepted

1 vote
Answer accepted
Dirk Ronsmans Community Leader Jan 14, 2021

Hi Stanislav,

What exactly would the outcome be? Just the issues under that security level?

I'd say that you don't even need to mention it then.. if the user using that filter doesn't have access they won't see them or does have access to a certain level they will appear. 

The filter will only apply to what security level the current user has access to.

The originaly i want a person see issues that are attached to his group or role. But i dont now how to connect issue to this. And i decided to linked issues with the security level. And than add role to the security level so than he can see the issues.

Reporter create issue and mark the security level. And i want a filter to be like :

status=to do and level= (security level of the person who is using filter)

or it dosent have sence ?

Dirk Ronsmans Community Leader Jan 14, 2021

Imho, it doesn't really make sense.

A security level is a way to really block other users (that are not part of the level) to see the issues. So if you created one for each user other users will not see the tickets anymore. (it's like they don't exist to them)

Since you made it as a security level if the user creates a filter/executes a filter all other items will automatically be filtered out.

so just putting status = "to do" would be enough

 

If however you just want users to have a way to group their tickets together and filter on them but not limit who can see them you might just make a custom field like "group" or "role" or "knowledge domain"... 

if it is attached to the person itself you could create groups in JIRA, add the users to those groups so they are functionally combined/together and then set up a custom field of type group picker where you enter it.

Once that is implemented you can make a filter such as currentUser() = memberOf("groupname")

 

So unless you really want to block the issues from being seen by anyone else the security level might be overkill.

Like Nicolai Nekrasov likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
Community showcase
Posted in Jira Software

Presenting the "Best of 2020" Jira Software roundup!

Catch up with Atlassian Product Managers in our 2020 Demo Den round-up! From Advanced Roadmaps to Code in Jira to Next-Gen Workflows, check out the videos below to help up-level your work in the new ...

7,120 views 8 28
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you