Error when trying to create a subtask using the inline Create button

[Keith Hodge]

When using the Scrum board inline + Create under a parent issue to create a sub-task, Jira opens the create dialog without a project selected. The dialog immediately displays "The issue type selected is invalid". If a project is manually selected, Jira opens the standard issue creation form (Story/Bug/Task etc.) instead of the Sub-task form. Network response contains:

1 {

2 "errorMessages": [

3 "key not found: 'jira.user.gic.modernised.create.always-open-fallback-view.spotlight'"

4 ],

5 "errors": {}

6 }

Creating sub-tasks from within the parent issue works normally. The issue affects all users and multiple browsers.

[joris raffin]

Hi Keith,

I haven't been able to find any public Atlassian documentation or known bug referencing the internal key:

"jira.user.gic.modernised.create.always-open-fallback-view.spotlight"

However, the key name appears to be related to Jira Cloud's new "Modernised Create" / Global Issue Create (GIC) experience that Atlassian has been rolling out recently. Atlassian's documentation and community announcements mention significant changes to the issue creation workflow, including the new quick-create dialog. 

https://community.atlassian.com/forums/Jira-articles/Introducing-the-new-streamlined-Create-experience-in-Jira/ba-p/3256211 

A few things stand out in your description:

• The issue affects all users and browsers.
• The project is not automatically selected.
• Jira falls back to a regular issue creation dialog instead of a Sub-task dialog.
• Creating a sub-task from within the parent issue still works.

That combination suggests the Scrum board's inline + Create action may be losing the parent/project context before the create dialog is initialized.

I would recommend checking:

• Whether the issue occurs on all Scrum boards or only a specific board.
• Whether the board is single-project or multi-project.
• Whether the Sub-task issue type is still present in the project's Issue Type Scheme.
• Browser network traces (HAR) to identify which request returns the "key not found" response.

Since the error references an apparently internal feature flag and the problem is reproducible across users and browsers, this looks more like a Jira Cloud regression than a local configuration issue.

If you can reproduce it consistently, I would recommend opening an Atlassian Support ticket.