MENU
[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.)
Suggested Answer: B, C, D
Get Premium ACP-120 Questions
as Interactive Web-Based Practice Test or PDF
Real Exam Format
Detailed Explanations
Instant Access
Get Your Practice Test
29 comments · newest first
JU
Julio
10 months ago
Wait, are we sure it's not an issue security scheme? Seems odd.
JE
Jeniffer
10 months ago
Custom field context is a likely culprit as well.
CO
Cory
10 months ago
I think project permissions might be the issue too.
AM
Amber
11 months ago
I agree with the first three, but I'm skeptical about the last one.
CE
Ceola
11 months ago
Definitely could be field configurations causing this.
GL
Glory
11 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.
DA
Daron
11 months ago
Custom field context sounds familiar. I think it can limit which fields show up based on the project or issue type.
VI
Viola
11 months ago
I'm not entirely sure, but I think project roles might affect visibility too. We practiced a question like this in class.
RI
Rikki
12 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.
CO
Coral
12 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.
BE
Benton
12 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.
BL
Blythe
1 year 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.
AL
Alease
1 year 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.
ES
Estrella
1 year ago
Project roles, project permissions, and custom field context - the holy trinity of Jira configuration headaches.
KA
Kara
1 year ago
C) Custom field context
RO
Ronald
1 year ago
B) Field configurations
TY
Tyisha
1 year ago
A) Project roles
LE
Leonie
1 year ago
Custom field context, for sure. Jira likes to keep you on your toes with all those field settings.
LY
Lynsey
1 year ago
C) Custom field context
RO
Romana
1 year ago
B) Field configurations
EL
Elli
1 year ago
A) Project roles
AN
An
1 year ago
I bet it's the project permissions. Sounds like someone forgot to grant the necessary access to the users.
KA
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?
HI
Hillary
1 year ago
C) Custom field context
TE
Teddy
1 year ago
B) Field configurations
LI
Lindy
1 year ago
A) Project roles
IL
Iluminada
1 year ago
Custom field context could also be a possible root cause.
BR
Brittani
1 year ago
I believe field configurations might be the issue.
JO
Joaquin
1 year ago
I think the root cause could be project roles.