Cannot create issues using the "+ create issue" feature in the backlog

[Oscar Albrecht]

Hi,

I am setting up Jira for multiple teams in my company.

Some projects are able to create issues using the "quick" creation ("+ create issue" link in the backlog) and some are not.

When I try to create, the "normal" modal opens with the "project" and "issue type" fields with the correct project and issue type selected, but a message "No Project Selected" and "Issue type is invalid". If you ignore it and press enter, the issue gets created.

I do not know what is the difference between the projects where it works and the ones where it doesn't. Some projects have been renamed, *maybe* this is the issue.

How can I fix it so everyone can use the quick issue creation feature?

[Robert Kalweit]

This thread already helped me and pointed me in the right direction.
When the problem occurred my filter was sth. like:

project = P1 and someOtherCriteria OR subtasksOf(someOtherCriteria)

I've found out how to fix it for me. A simple bracket did the trick:

project = P1 and (someOtherCriteria OR subtasksOf(someOtherCriteria))

This causes the first one -> project = P1 to always be true. After this change already the board configuration tells you "this board is only in Project P1". And since this is finally determined now, I can create issues from the backlog again.

[Eleanor Kauffman]

@Oscar Albrecht We've also run into this same issue.   I've been able to isolate that the error looks to be occurring for boards that have filters using the ScriptRunner JQL function epicsOf ( project = XXXX or (issueFunction in epicsOf("project = XXXX")) ).  Are you seeing similar differences with filters for your impacted boards?  I'm still investigating more as we do need to use that function.

[Oscar Albrecht]

Hi @Eleanor Kauffman 

Yes, this is exactly the problem. I contacted Atlassian and the workaround is to include the project in the filter.

[Mohamed Adel]

@Oscar AlbrechtYou need to check the permission scheme for this project and your assigned project roles. Also, you can try the permission helper it can give you a clear justification..

i hope this will help 

[Oscar Albrecht]

Hi, thanks for your message.

It does not seem to be a permission problem, since:

1- Nobody can create issues using the link, even if I try as administrator.

2- When the modal opens, if you click on "create", it will work. So the users have the permission to create.

It seems a configuration problem (or a bug).