Deal of The Day! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Atlassian ACP-120 Exam - Topic 5 Question 6 Discussion

[Issue Types, Fields, Screens]Users need to be able to select Browser Type when editing bugs in the DEV project. However, they cannot see the field. Identify three possible root causes. (Choose three.)
B) Field configurations and C) Custom field context and D) Project permissions
A) Project roles
E) Issue security scheme

Atlassian ACP-120 Exam - Topic 5 Question 6 Discussion

Actual exam question for Atlassian's ACP-120 exam
Question #: 6
Topic #: 5
[All ACP-120 Questions]

[Issue Types, Fields, Screens]

Users need to be able to select Browser Type when editing bugs in the DEV project. However, they cannot see the field. Identify three possible root causes. (Choose three.)

Show Suggested Answer Hide Answer
Suggested Answer: B, C, D

by Gaston at Jun 11, 2025, 01:51 AM

Limited Time Offer

25%

Off

Get Premium ACP-120 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Julio
8 months ago
Wait, are we sure it's not an issue security scheme? Seems odd.
upvoted 0 times
...
Jeniffer
8 months ago
Custom field context is a likely culprit as well.
upvoted 0 times
...
Cory
9 months ago
I think project permissions might be the issue too.
upvoted 0 times
...
Amber
9 months ago
I agree with the first three, but I'm skeptical about the last one.
upvoted 0 times
...
Ceola
9 months ago
Definitely could be field configurations causing this.
upvoted 0 times
...
Glory
9 months ago
I wonder if project permissions could be the issue here. I feel like we discussed how they can restrict access to certain fields.
upvoted 0 times
...
Daron
10 months ago
Custom field context sounds familiar. I think it can limit which fields show up based on the project or issue type.
upvoted 0 times
...
Viola
10 months ago
I'm not entirely sure, but I think project roles might affect visibility too. We practiced a question like this in class.
upvoted 0 times
...
Rikki
10 months ago
I remember something about field configurations being a common issue when fields aren't visible. That could definitely be one of the causes.
upvoted 0 times
...
Coral
10 months ago
I've seen issues like this before. My strategy is to methodically go through each of the possible causes and eliminate them one by one until I find the root problem.
upvoted 0 times
...
Benton
10 months ago
Project permissions and issue security scheme could also be factors. I'll make sure to review those as well to identify the root cause.
upvoted 0 times
...
Blythe
11 months ago
Okay, let's see. The field could be hidden due to project roles, field configurations, or custom field context. I'll need to check those areas first.
upvoted 0 times
...
Alease
11 months ago
Hmm, this seems like a tricky one. I'll need to think through the different configuration settings that could be causing the issue with the Browser Type field.
upvoted 0 times
...
Estrella
1 year ago
Project roles, project permissions, and custom field context - the holy trinity of Jira configuration headaches.
upvoted 0 times
Kara
1 year ago
C) Custom field context
upvoted 0 times
...
Ronald
1 year ago
B) Field configurations
upvoted 0 times
...
Tyisha
1 year ago
A) Project roles
upvoted 0 times
...
...
Leonie
1 year ago
Custom field context, for sure. Jira likes to keep you on your toes with all those field settings.
upvoted 0 times
Lynsey
1 year ago
C) Custom field context
upvoted 0 times
...
Romana
1 year ago
B) Field configurations
upvoted 0 times
...
Elli
1 year ago
A) Project roles
upvoted 0 times
...
...
An
1 year ago
I bet it's the project permissions. Sounds like someone forgot to grant the necessary access to the users.
upvoted 0 times
...
Kanisha
1 year ago
Hmm, gotta be the field configurations. Jira can be a real pain when it comes to managing fields, am I right?
upvoted 0 times
Hillary
1 year ago
C) Custom field context
upvoted 0 times
...
Teddy
1 year ago
B) Field configurations
upvoted 0 times
...
Lindy
1 year ago
A) Project roles
upvoted 0 times
...
...
Iluminada
1 year ago
Custom field context could also be a possible root cause.
upvoted 0 times
...
Brittani
1 year ago
I believe field configurations might be the issue.
upvoted 0 times
...
Joaquin
1 year ago
I think the root cause could be project roles.
upvoted 0 times
...

Save Cancel