-
Bug
-
Resolution: Fixed
-
Medium
-
5.17.5, 10.3.2
-
7
-
Severity 2 - Major
-
46
-
Problem
When moving issues with Asset Custom Fields that have Filter Issue Scope defined, it fails to move the issue due to error Could not find Asset object/s.
This issue does not occur in JSM 5.12.
Environment
JSM 10.x
Steps to Reproduce
- Import object schema jsm-error-move-issue-obj-sche_2025-02-13T02_14_04.814Z.zip
- Create 2 Asset custom fields and associate them with Create/View screens:
- Create a ticket with the Product and Model fields filled:
- Move this ticket to another issue type in the same project:
Expected Results
In JSM 5.12 (Jira 9.12), the Move Issue screen does not prompt updating the Model field:
This is expected as both Product and Model are not required fields.
Actual Results
In JSM 10 (Jira 10), the Move Issue screen prompts updating the Model field:
After selecting a value from the dropdown menu, it prompts error Could not find Asset object/s and the Move Issue process can't proceed:
Workarounds
Disable the dark feature assets.aql.scope.filtering.on.issue.update by:
- Going to the page: <JIRA_BASE_URL>/secure/SiteDarkFeatures!default.jspa
- Adding assets.aql.scope.filtering.on.issue.update.disabled to the list of dark features
- is duplicated by
-
JSDSERVER-16167 Moving a Jira issue fails with the error message "Could not find Assets object/s."
-
- Closed
-
- links to