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 does not use default value when project is switched on create issue screen

Adolfo Casari

I have a customfield with 2 contexts.

When creating an issue in the popup window, if I change the project, the default value for the customfield that correspond to that project according to the context is not show (shows None). I have to close the popup and open again to see the default value show up correctly.

This is Jira 5.2.

Is this a known bug and has it been fixed in any version?

Thanks in advance,

Accepted answers

EddieW_h8oivr

I am not aware, nor could find any open bug. You may want to create one at jira.atlassian.com.

A workaround is to pre-populate the project on the create screen with a link that includes ?pid=XXXX

https://confluence.atlassian.com/display/JIRA/Creating+Issues+via+direct+HTML+links

All comments

EddieW_h8oivr

I am not aware, nor could find any open bug. You may want to create one at jira.atlassian.com.

A workaround is to pre-populate the project on the create screen with a link that includes ?pid=XXXX

https://confluence.atlassian.com/display/JIRA/Creating+Issues+via+direct+HTML+links

unknown

I second this issue. The create issue pop-up will load with pre-configured defaults for whatever project you are currently in. If you change the project in the dropdown, it will not switch to the defaults set to that project. This leaves the user to have to clear the fields manually and then input the data from memory.

Christopher Can1

Hello Adolfo, did you by chance create a ticket for this? I have run into the same issue and wanted to be sure I did not submit a duplicate ticket. Thanks!

Adolfo Casari

As far as I remember this is still a known bug in 6.X and there is an issue opened (don't have the url at hand now).

George Lewe (LSY)

Just for info. This bug has been reported to Atlassian here:

https://jira.atlassian.com/browse/JRA-30942

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

custom-field

jira