-
Bug
-
Resolution: Won't Fix
-
Low
-
None
-
3
-
Severity 3 - Minor
-
0
-
Issue Summary
Sending a PATCH request to Insight's External Imports will clear the “Filter data source by IQL“ setup on Object Type mappings
Steps to Reproduce
- Setup an External Import in Insight
- After setting up the Object Type mapping, via the UI click the three-dotted icon and then on Edit object type mapping
- Add an IQL to the "Filter data source by IQL"
- Send a PATCH request to update the Import configuration
Expected Results
Import configuration is updated as expected
Actual Results
Import configuration is updated as expected, but the "Filter data source by IQL" field is cleared.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- is related to
-
JSDCLOUD-11891 Add ability to set "Filter data source by IQL" via REST on External Imports
- Gathering Interest
[JSDCLOUD-11890] Sending a PATCH request to Insight's External Imports will clear the “Filter data source by IQL“ setup on Object Type mappings
Hi Oliver,
this is very bad news. Due to not solving this issue, my import configuration in Assets is just a mess. It is very annoying that you offer a Rest-API, but you are not willing to fix bugs. Perhaps that's the reason, why there is so little interest in the Rest-API for Assets, as it is very painful and time consuming to set up.
The import functionality in Insight for Server was way better, then the import functionality in Assets Cloud. Migration Insight Server to Assets Cloud was very, very, very time consuming and has cost us a significant amount of money, as we had to get support from one of our suppliers.
moving from JSM Server to JSM Cloud: Assets Cloud ... (atlassian.com)
Chris
Hi everyone,
This is Oliver from the Jira Service Management / Assets team. Thank you for previously raising this bug to our attention. To set the right expectations, we are closing this bug to focus on our upcoming roadmap for all Jira Service Management / Assets users.
If this is still an issue for you, please let us know. Thank you again for providing valuable feedback to our team!
Thank you,
Oliver Senn
Dear @Augusto,
thank you very much for adding this bug.
My workaround: preparing the source data in a way, so that no filtering is nessecary. The filtering will be done, before using the REST-API. I will need to set up the REST-API for several uploads...
Chris
for those who want to re-vote on this bug, the new ticket looks to be this one: JSDCLOUD-12603