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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

Security concerns Jira Align

Hello All,

The company i work for is considering to switch to Jira Align. I have talked to an ex colleague of mine who is already using it and think it's a great product. However he was not sure about my question so maybe someone can help me out on this.

When Jira align we want certain stories/issues to be only available to one sector given the sensitivity of the content. Our R&D department wants that only a set of people can see their tickets and not the whole company (e.g. general IT). So my question: is it possible to use a feature similar to "issue security scheme" in Jira Software, that restricts users from seeing certain cards?

I was not able to find an answer to that question in the available documentation online, so really hoping that someone can help me out on this.

1 answer

1 vote

The team --and the teams level in the organizational structure --are typically used to control who can and cannot see work.  The possibility exists to also create "private" portfolios which can further restrict who can see the work.

Thank you Allan, this clarifies my question. Any chance there is some official documentation available about this or an article with the best practices, so I can share and discuss this with the other scrum masters in my company?

I would start with the Assign Team Roles article.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events