-
Bug
-
Resolution: Fixed
-
Medium
-
28
-
Severity 2 - Major
-
93
-
Summary
If you click to delete a Screen Scheme but you associate it with an Issue Type Screen Scheme before it is deleted, Jira will let you delete the Screen Scheme.
If the Issue Type Screen Scheme is being used by any project, all "Screens" page of project settings will be blank.
Steps to Reproduce
- Click to Delete a Screen Scheme. You'll be taken to this page:
- On another tab, associate this Screen Scheme to an Issue Type Screen Scheme, as shown in the screenshot below:
- Go back to the other tab and complete the deletion of the Screen Scheme.
Expected Results
Jira should not let you delete the Screen Scheme since it's associated with an Issue Type Screen Scheme.
Actual Results
The Screen Scheme will be deleted and the Issue Type Screen Scheme will be shown as a blank:
If the Issue Type Screen Scheme is associated with any project, the "Screen" tab of every project settings will be blank:
It will also not be possible to create an issue of that issue type in the projects associated with the Issue Type Screen Scheme.
Whenever you try to create an issue, the following error will be thrown:
java.lang.IllegalArgumentException: eq(null) is not allowed. Use isNull() instead java.lang.IllegalArgumentException: eq(null) is not allowed. Use isNull() instead at com.querydsl.core.types.dsl.SimpleExpression.eq(SimpleExpression.java:127) at com.atlassian.jira.issue.fields.screen.QueryDslFieldScreenSchemeManager.lambda$getFieldScreenScheme$2(QueryDslFieldScreenSchemeManager.java:74) at com.atlassian.jira.database.DefaultQueryDslAccessor.lambda$executeQuery$0(DefaultQueryDslAccessor.java:55) at com.atlassian.jira.database.DatabaseAccessorImpl.lambda$runInTransaction$0(DatabaseAccessorImpl.java:71) at com.atlassian.jira.database.DatabaseAccessorImpl.executeQuery(DatabaseAccessorImpl.java:40) at com.atlassian.jira.database.DatabaseAccessorImpl.runInTransaction(DatabaseAccessorImpl.java:66) at com.atlassian.jira.database.DefaultQueryDslAccessor.executeQuery(DefaultQueryDslAccessor.java:54) at com.atlassian.jira.issue.fields.screen.QueryDslFieldScreenSchemeManager.getFieldScreenScheme(QueryDslFieldScreenSchemeManager.java:72) at com.atlassian.jira.issue.fields.screen.CachingFieldScreenSchemeManager.lambda$getFieldScreenScheme$2(CachingFieldScreenSchemeManager.java:44) at com.atlassian.vcache.internal.core.metrics.TimedSupplier.get(TimedSupplier.java:32) at com.atlassian.vcache.internal.core.service.DefaultRequestCache.lambda$get$2(DefaultRequestCache.java:52) at java.util.Optional.orElseGet(Optional.java:267) at com.atlassian.vcache.internal.core.service.DefaultRequestCache.get(DefaultRequestCache.java:50) at com.atlassian.vcache.internal.core.metrics.TimedLocalCacheOperations.get(TimedLocalCacheOperations.java:64) at com.atlassian.jira.issue.fields.screen.CachingFieldScreenSchemeManager.getFieldScreenScheme(CachingFieldScreenSchemeManager.java:44) at com.atlassian.jira.issue.fields.screen.issuetype.IssueTypeScreenSchemeEntityImpl.getFieldScreenScheme(IssueTypeScreenSchemeEntityImpl.java:81) at com.atlassian.jira.issue.fields.screen.issuetype.DefaultIssueTypeScreenSchemeManager.getFieldScreenSch
Workaround
It's not possible to fix this through the UI as if you try to change the Screen Scheme it'll take you to a 500 error page.
Contact our support so we can apply the workaround in your instance since it requires an update on the database to fix the Issue Type Screen Scheme.
