Details
-
Bug
-
Resolution: Unresolved
-
Low
-
5.13.1
-
3
-
Severity 3 - Minor
-
10
-
Description
Issue Summary
Bulk update of issues to change Assets customfield value fails, if the assets custom field configuration has an AQL in the "Filter Issue Scope (AQL)".
This is reproducible on Data Center: yes
Steps to Reproduce
- Create an Assets schema, with a new object type, and add some 4-5 objects to it
- Create an assets custom field with configuration as below.
- Associate this custom field with a project and add it to the create and view screens.
- Create 2 new issues in Jira project, and add value to this Assets custom field.Â
- Fetch the issues as below, and perform a bulk change to edit both issues together.
 - Select a new value in the drop-down of the assets custom field.Â
- Hit "Next"
Expected Results
We go to the next page without any issue and the issues are all updated with new assets object.
Actual Results
There is an Error in the UI with a 500 Error code.
The below exception is thrown in the xxxxxxx.log file:
2024-03-20 12:46:58,548+0000 http-nio-8080-exec-2 url: /jsm/internal-error ERROR [c.a.j.web.servlet.InternalServerErrorServlet] {errorId=53ca7afc-d583-4b08-9b43-375c641f3bc9, interpretedMsg=, cause=java.lang.NumberFormatException: For input string: "", stacktrace=java.lang.NumberFormatException: For input string: ""
at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:65) [?:?]
at java.base/java.lang.Long.parseLong(Long.java:702) [?:?]
at java.base/java.lang.Long.valueOf(Long.java:1144) [?:?]
at com.riadalabs.jira.plugins.insight.services.jira.fields.RequestFieldIssueRepresentation.getOptions(RequestFieldIssueRepresentation.java:146) [?:?]
at com.riadalabs.jira.plugins.insight.services.jira.fields.InsightJiraFieldManagerImpl.getCustomerFieldValues(InsightJiraFieldManagerImpl.java:178) [?:?]
at com.riadalabs.jira.plugins.insight.services.jira.fields.InsightJiraFieldManagerImpl.replacePlaceholders(InsightJiraFieldManagerImpl.java:358) [?:?]
at com.riadalabs.jira.plugins.insight.services.jira.fields.InsightJiraFieldManagerImpl.replacePlaceholdersFromIql(InsightJiraFieldManagerImpl.java:271) [?:?]
at com.riadalabs.jira.plugins.insight.services.jira.customfield.DefaultObjectCustomField.getIqlWithPlaceHolderSubstitution(DefaultObjectCustomField.java:815) [?:?]
at com.riadalabs.jira.plugins.insight.services.jira.customfield.DefaultObjectCustomField.getIssueScopeIql(DefaultObjectCustomField.java:809) [?:?]
at com.riadalabs.jira.plugins.insight.services.jira.customfield.DefaultObjectCustomField.getcustomFieldScopedIql(DefaultObjectCustomField.java:855) [?:?]
at com.riadalabs.jira.plugins.insight.services.jira.customfield.DefaultObjectCustomField.isValidObjectBeanScope(DefaultObjectCustomField.java:872) [?:?]
at com.riadalabs.jira.plugins.insight.services.jira.customfield.DefaultObjectCustomField.determineObjectBean(DefaultObjectCustomField.java:758) [?:?]
at com.riadalabs.jira.plugins.insight.services.jira.customfield.DefaultObjectCustomField.validateFromParams(DefaultObjectCustomField.java:590) [?:?]
at com.atlassian.jira.issue.fields.ImmutableCustomField.validateParams(ImmutableCustomField.java:713) [classes/:?]
at com.atlassian.jira.web.action.issue.bulkedit.BulkEdit.validateInput(BulkEdit.java:353) [classes/:?]
at com.atlassian.jira.web.action.issue.bulkedit.BulkEdit.doDetailsValidation(BulkEdit.java:254) [classes/:?]
Workaround
- Remove the AQL from Filter Issue Scope (AQL) of the assets configuration, if it is not dependent on any other fields of the issue. Add the same to AQL to "Filter Scope (AQL)".
- If the AQL from "Filter Issue Scope (AQL) " is needed, then the issues need to edited individually.
Attachments
Issue Links
- mentioned in
-
Page Loading...