BlackFriday 2024! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions

Atlassian Exam ACP-100 Topic 1 Question 97 Discussion

Actual exam question for Atlassian's ACP-100 exam
Question #: 97
Topic #: 1
[All ACP-100 Questions]

Critical production bugs in a Jira Software project are hidden with an issue security scheme that has a single

security level.

Only project administrators are listed in the security level and granted the Set Issue Security permission.

A new requirement states that a few other Jira Core users, who have Browse Projects permission, should be able to see the hidden issues. These users will vary per issue and be selected from across various groups.

What needs to be added to the security level?

Show Suggested Answer Hide Answer

Contribute your Thoughts:

Rupert
1 months ago
D) Project role is the way to go. Keeps things nice and organized, you know? Plus, it's the most 'Jira-y' solution, if you ask me.
upvoted 0 times
Franklyn
13 days ago
D) Project role
upvoted 0 times
...
Brandon
15 days ago
C) Group custom field value
upvoted 0 times
...
Danica
28 days ago
B) User custom field value
upvoted 0 times
...
Marlon
30 days ago
A) Application access
upvoted 0 times
...
...
William
2 months ago
I don't know, man. This whole security thing sounds like a headache. Can we just use the Force to make the issues unhide themselves?
upvoted 0 times
Noel
8 days ago
User1: Agreed, it's the best option to give access to specific users while maintaining security.
upvoted 0 times
...
Helaine
9 days ago
User3: Yeah, adding Group custom field value is the way to go to solve this security issue.
upvoted 0 times
...
Joye
10 days ago
User2: That's a good idea. It will allow selected users from different groups to see the hidden issues.
upvoted 0 times
...
Jamal
1 months ago
We can't use the Force, but we can add Group custom field value to the security level.
upvoted 0 times
...
...
Zachary
2 months ago
I think Project role could also be added to the security level to give specific permissions to certain roles.
upvoted 0 times
...
Marisha
2 months ago
Hmm, I'm leaning towards F) Group. It's a classic way to manage access, and it's probably the most straightforward option here.
upvoted 0 times
Daren
18 days ago
Group sounds like the best option for adding those Jira Core users to the security level.
upvoted 0 times
...
Deeanna
19 days ago
I agree, using a group custom field value would make it easier to manage access for different users.
upvoted 0 times
...
Kattie
30 days ago
I think F) Group is a good choice. It allows for flexibility in selecting users from different groups.
upvoted 0 times
...
...
Katina
2 months ago
C) Group custom field value is the way to go. This allows you to dynamically assign groups to the security level, making it more flexible.
upvoted 0 times
...
Chau
2 months ago
I agree with Rosendo, adding Group custom field value would allow us to select users from various groups.
upvoted 0 times
...
Laurel
2 months ago
E) Single Users seems like the easiest solution. Why bother with project roles when you can just add the individual users who need access?
upvoted 0 times
Mayra
30 days ago
E) Single Users seems like the easiest solution. Why bother with project roles when you can just add the individual users who need access?
upvoted 0 times
...
Sheldon
1 months ago
F) Group
upvoted 0 times
...
Dorothy
1 months ago
E) Single Users
upvoted 0 times
...
Julio
1 months ago
A) Application access
upvoted 0 times
...
...
Rosendo
2 months ago
I think we should add Group custom field value to the security level.
upvoted 0 times
...
Annette
2 months ago
I think the answer is D) Project role. This way, you can assign specific project roles to access the hidden issues, rather than relying on a single security level.
upvoted 0 times
Daniel
1 months ago
Yes, project roles would be the best option to add to the security level for this scenario.
upvoted 0 times
...
Hailey
2 months ago
I agree, using project roles would allow for more flexibility in granting access to the hidden issues.
upvoted 0 times
...
...

Save Cancel