Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
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,
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
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.
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs