Це відео не доступне.
Перепрошуємо.
Simplified Issue Level Security - Prevent Unauthorized Access!
Вставка
- Опубліковано 8 жов 2023
- Learn how to lock up issues in Jira.
😀If you are enjoying the content and want to help support the channel, check out the links down below!
👨🏫Udemy
🔴 Jira Fundamentals Course - www.udemy.com/course/jira-clo...
🛒Apetech Merch Store
🔴 my-store-dc4aec.creator-sprin...
✅Subscribe to The Jira Life
🔴 / @thejiralife
👇And don’t forget to check out channel sponsors down below!
Released
🔴 released.so?
💲Discount Code: RARNAPETECH
#jira #atlassianjira #automation
To get more resources and get in contact with me check out this link linktr.ee/apetech
It's been a year of watching your videos and I must say I have become quite the Jira Admin for my company. I have zero Jira experience, but from really taking in the information you have provided I have been able to tighten up the mess and make our Jira use more efficient. I am starting to feel comfortable around Jira.
What an awesome comment! Thanks for sharing and letting me know! It means so much!! I hope that the rest of my videos provide the same amount of value!
thanks dude, atlassian community didn't help.
It is all about the field 'security level'
What I did, if any help to anyone else was:
1. Created an approval board, and only wanted people who submitted issues and the people on the approval chain to see the ticket
2. Two custom work flows for each ticket type, where when one is finished it creates the next ticket and carries over the fields (which all need security)
3. Then have 4 custom fields, which are required when move to second status, since status one is a 'to-do', however still only want the reporter to see their ticket then
4. So created a issue security scheme, where the people in each custom field (which are also used for transitions and post work), admin group, and finance group can see them.
5. created an automation for when new tickets were created to set security level.
It kept failing, I was stuck, nothing would work, everyone could see all tickets
I then saw here to add the security level field...and that did the trick.
I can even go back and lock-down existing tickets.
I am still watching the video and I have reached the point where you ask about my use case. Firstly, I would like to thank you for the informative video. However, my situation is quite the opposite. I work for a software company and we have recently decided to grant our customers access to Jira. Unfortunately, the decision-makers didn't consider the potential consequences. We don't want to give our customers access to everything. Ideally, we would like to have control over what they can see by implementing a level or tag system that limits their access to specific issues that we have designated. For example, we would like to tag issues that only pertain to a particular customer for them to view. But all projects are already set up, some for a while now
I would love to have a simple way to lock all issues related to the project group "customer". Whenever someone adds a label or any other possible thing for the automation, the issue should be visible to the project role "customer". This will help us create specific overviews for meetings or provide access, while ensuring that customers can only see the items that we decide to share with them.
hi, can you post the video about the other situation? i want to restrict the project to some users and open them only specific ticket , for exp to view only the tickets that they are the reporters
I am also keen on the second option. I have such a need in my teams to give access for external users only to selected issues within the project. So that they do not have access to the other issues.
Hey, I also would love to see video about second more difficult option ;)
@ApetechTechTutorials - I really would like to see the "hard version" - i.e., I'm in HR and I need everything LOCKED and then allow only certain users/groups to see individual cards. By the way, I am using Jira WORK Management, not Service Mangement, if that makes a difference.
As many have said, I fall under the use case where all tickets under a specific category are locked but only a select few users are able to access them.
Awesome look at Issue Security!
Thank you for this video! It helped me a lot =)
Yes I fall in that use case , please gives us a overview
My rule is looking all the tickets, regardless of having an automation rule
Hi my use case is I want everyone to see the issues but one user until the issues has changed status to open. Once admin change issue status to open then that particular must be given the view of that particular issue
This has been one of the pet peeves of mine with Jira - how do I share a project plan with outsiders - perhaps going as far as ones that do not have a Jira account - any tips would be more than appreciated!
Hey Alex! I'm really enjoying your videos, you taught me a lot and I'm applying for your courses in Udemy soon. I've been trying to set this up, same as in the video, everything is done, all fields added, cross-checked everything, however when I try to create the Automation rule, on the last step there's no Security Level appearing, it stays the same. I've checked everything you are doing in the video, even additionally checked if the Security Level field is not hidden etc., however no luck. Any advise?
I have a use case where I want to create a limited org admin where I want them to be able to handle stuff such as external app integrations but not able to view a specific confidential project. If anyone knows how to guide me through this please let me know. Much appreciated!
Hey Alex, I really enjoy your videos and learn lot from it. I want to know if in any way is it possible to have an issue security or permission for specific persons on selected issues only in Team managed software. please, reply me asap!!
Not that I'm aware of. If it's not in the project settings then it's not possible.
Thanks for getting back to me! I found the restriction feature for issues in Team-managed software, and it's functioning differently from permission schemes. Nonetheless, I can still effectively manage with it. Looking forward to upcoming videos on dashboard gadgets!