nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Custom field showing up on one screen not the other, even though using the same field configuration

Shreena Patel1

I'm creating a specific screen for customers to report a bug into our system (anonymous users). I have an issue type scheme with two issue types- bug and improvement. The screens are meant to look identical. So I have one Create Issue Screen with my selected fields including my custom field "email". This email field shows up for the "Bug" issue type but for 'Improvement' it is missing (I see the other fields just not this one). Could you help me please?Does it have something to do with using improvement in a different project with a different looking screen and different configuration? Would apprecaite your support.

Thanks,

Shreena

Accepted answers

Jobin Kuruvilla [Adaptavist]

Is the field available for all issuetypes? Or is it tied to Bugs alone?

All comments

Jobin Kuruvilla [Adaptavist]

Is the field available for all issuetypes? Or is it tied to Bugs alone?

Jobin Kuruvilla [Adaptavist]

See https://confluence.atlassian.com/display/JIRA/Configuring+a+Custom+Field#ConfiguringaCustomField-Context

Shreena Patel1

Under custom fields it is linked to bug issue type. This must be why. How do i add improvement issue type under available context(s).

Shreena Patel1

I've sorted it sorry. Thank you. Just needed to go to edit configuration and select it from there.