-
Suggestion
-
Resolution: Duplicate
-
None
Issue Summary
The automation rule to clone issues throws the following error message even when the issue was cloned successfully and the problem field skipped:
Unknown fields set during clone, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -
Description (description)
Although this may prevent silent data loss, it is a bit misleading especial in email notifications.
Steps to Reproduce
- Trigger: new issue is created
- Action: Clone issue and specify a field that does not exist in the target issue screen.
Expected Results
We expect the following error message:
successful with some errors. Unknown fields set during clone, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored -
Description (description)
Actual Results
The below exception is thrown in the rule's audit log
Unknown fields set during clone, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored - Description (description)
Workaround
No workaround
- duplicates
-
AUTO-36 Improve Automation audit log - include more info, option to include additional detail in audit logs / issue history, keep history for more than 90 days
- In Progress
- is related to
-
JIRAAUTOSERVER-798 Automation rule error message misleading
- Gathering Interest
[AUTO-623] Automation rule error message misleading
Resolution | New: Duplicate [ 3 ] | |
Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
Link | New: This issue is related to JIRAAUTOSERVER-798 [ JIRAAUTOSERVER-798 ] |
Labels | New: jsw-s13 |
Component/s | Original: Jira Platform - Frontend - Framework [ 67093 ] | |
Key |
Original:
|
New:
|
Support reference count | Original: 3 | |
Project | Original: Jira Cloud [ 18514 ] | New: Automation for Cloud [ 22610 ] |
Support reference count | Original: 2 | New: 3 |
Support reference count | Original: 1 | New: 2 |
Support reference count | New: 1 |