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; } } }

Team Managed Project: Default value for Cascading field not being used

ヴァリエンテフロリアン_Florian Valiente_

I am pretty sure this was working up until last week, but today, in a team-managed project, cascading dropdown defaults are not being displayed when creating a new issue.

They are also not being set on save.

Default values for a normal dropdown is working fine.

Is this happening to anyone else?

Screenshot 2026-04-16 at 7.26.51 pm.png

Screenshot 2026-04-16 at 7.31.21 pm.png

Accepted answers

All comments

Arkadiusz Wroblewski

@ヴァリエンテフロリアン_Florian Valiente_

If that has worked until recently then proper Way is to Adress that to Atlassian cus it will be then Regress in Functionality.

ヴァリエンテフロリアン_Florian Valiente_

@Arkadiusz Wroblewski yeah, just finished creating a support issue as well!

Arkadiusz Wroblewski

@ヴァリエンテフロリアン_Florian Valiente_

We had a few incidents over the last two weeks that affected multiple services.

From my experience, some instances take longer than others to fully recover afterward. And if this was working before, I do not think it makes much sense to dig too deep into it right away, because at that point it is probably just a bug.

Bill Sheboy

Hi @ヴァリエンテフロリアン_Florian Valiente_

I recall there was a recent problem where the cascading field's default value did not display in the UX but it was present when the work item saved. That may be the same cause...or the defect has regressed as broken again. Perhaps let the Atlassian Support team know to check for that. If I find the defect ID I will update this post to add it.

Kind regards,
Bill

ヴァリエンテフロリアン_Florian Valiente_

@Bill Sheboy yeah, I did find one where they fixed the CMP default

JRACLOUD-98008 - Custom field's default value, defined within a specific context, is not appearing visually on the Create Issue screen, even though the value is correctly applied once the issue is saved

and it feels like the timing matches the time when this stopped working, so it feels like a regression

Bill Sheboy

As you are a Product Admin for a paid license level, I recommend directly contacting Atlassian Support to open a ticket for this defect regression:

https://support.atlassian.com/contact#/

When you hear back from them, please post what you learn to benefit the community. Thank you!

ヴァリエンテフロリアン_Florian Valiente_

@Bill Sheboy they've confirmed it is indeed a bug and have created a new ticket

https://jira.atlassian.com/browse/JRACLOUD-98094

Workaround:
-> Create an automation that sets the default value of the field!

ヴァリエンテフロリアン_Florian Valiente_

@Arkadiusz Wroblewski they've confirmed it is indeed a bug and have created a new ticket

https://jira.atlassian.com/browse/JRACLOUD-98094

Workaround:
-> Create an automation that sets the default value of the field!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud