Due to the configuration for this particular board, you'll have to use the full dialog to create a n

[Brendan]

When trying to create a new ticket from the backlog of our existing Kanban board.

Previously we could quickly enter the title of new issues on the board and fill in the detail later, but now we have to create all tickets using the full dialog UI.

Nothing had been changed with regards to this board, but we are getting an error message stating "Due to the configuration for this particular board, you'll have to use the full dialog to create a new issue" now.

In similar posts, the filter was identified as a cause of this problem.  The filter for this board is 

project in (ABC, XYZ) ORDER BY Rank ASC

Removing the 'in' statement and limiting the filter to include only one project will fix this, but that doesn't work for our users. 

Does anyone know how to get the original functionality back while still showing both projects on the board?

[Hernan Halabi - Elite IT Consulting Group · Accepted solution]

If you have more than one project you will have this behavior since you can't pick the project in which you are creating the ticket from the agile board interface

[darren.thatcher]

although a 2019 answer, and now is 2023, I thought I'd respond if it's useful to anyone:

I'm having the same problem in a Board that points to two Scrum Projects:

and in the Backlog view, I can see the Sprints from the two Projects, and I'm using the quick-create in one of those two Projects' Future Sprint.  So the Board software ought to know which underlying Project I'm trying to 'Create Issue' within...

anyway, I'll just leave this comment here, not expecting any response, my quest continues :)

[Hernan Halabi - Elite IT Consulting Group]

Hello Darren, as long as you can see 2 projects within a board you will have that problem. Since technically you can assign tickets from multiple projects into a single sprint, jira won't know by default in which project you want to quick create the ticket since anyone would apply based on the criteria above.

I know this won't solve the issue but hopefully explains the why

[ebarron]

So this is what I did to get this "fixed" on my Backlog view:

1. Made all custom fields optionals. (You may need to edit your Fields Scheme).
2. Create a Quick Filter on top that goes like this:
   project = XXX
   [[optional]] AND (issueType = bug OR issueType = story)
3. Then apply that quick filter and you are ready to add issues in bulk!