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,554,186
Community Members
 
Community Events
184
Community Groups

Preventing access to modify a User Story

What options are in-place to prevent a User in modifying a user story they are not assigned and belong to a different scrum team than owned by the user story?

2 answers

0 votes
Mark Cruth
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jul 23, 2020

Hi William!

For permissions in Jira Align, you can control whether or not a user has access to edit a work item (e.g. Story) based on their system role. For each system role you can give some people access to edit specific work item types and some read-only access. The caveat is that it's a universal thing...if you can edit you can edit all of those work items of that type (e.g. Story) or none of them (within the Portfolio you are part of). Based on your post I'm guessing you're looking to prevent a person on one team from editing the work on another team (even if they have the same system role and are within the same portfolio), which is not possible today. We do have pretty robust audit logs in Jira Align, so if someone does modify another teams issue (when they shouldn't), you will be able to see this in the audit log. 

Here's some additional info on permissions (if you'd like to learn more): 

https://agilecrafthelp.zendesk.com/hc/en-us/articles/115005996767-10X-Set-System-and-Team-Roles-Permissions

Also, if you'd like to submit an enhancement idea for this, here's an article that show you how to submit an idea through the Jira Align ideation portal: 

https://community.atlassian.com/t5/Jira-Align-articles/A-guide-to-Jira-Align-s-Ideation-portal/ba-p/1309475

Thanks and let me know if you have any questions.

Mark

0 votes
Nic Brough -Adaptavist-
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 22, 2020

Assuming you are using Jira at the story level, then your boards should be representing teams, with a single project underlying each one.  You can therefore set permissions on the projects that say "only members of this team can edit the issues"

What is the process for setting project permissions?

We are using Jira Align

Nic Brough -Adaptavist-
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 23, 2020

My answer is only useful if you are using Jira Software coupled with Jira Align.  If you are only using Align, please do ignore this thread!

To set permissions in Jira Software, you log in as an admin and go to either the permission scheme list in the admin section, or to the project admin and the permissions section.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events