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

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,462,572
Community Members
 
Community Events
176
Community Groups

How to set issue security level when users are from multiple project roles

I have a project, where the release(tickets) are created for their projects.

Once the ticket is created only users from those project group should be able to see, others no.

Ex: my project is "Release Manager

Other project is "Project1"

If the user from "Project1" creates a release registration with the release fix version in "Release  Manager", that ticket must be viewed only by the user group/project role in "Project1"

 

Please help me with solutions if anyone come across. Thanks in advance.

1 comment

@Nag, you would need to create a user group for each project (e.g. 'Project1 users').  You can look at the documentation for more details: Configuring issue-level security.

Thanks, I tried this option but the problem is project admins can not be able to add users to the group('Project1 users') every they come up with new users.

@Nag, project admins will only be able to add users to project roles. This will be limited to their project. The 'Release Manager' project has no visibility into 'Project1' roles.

Alternatively, the 'dirty' solution (I personally wouldn't recommend it) would be to grant all the project leads 'project administration' permission in the 'Release Manager' project.

The best solution would be to allow project leads to open a request in your support project (e.g. Atlassian support or Jira support). With post-functions and programming, the process can be entirely automated to add a user to the correct 'Project 1 Users' global group. (Groovy Example)

Comment

Log in or Sign up to comment