This has been an issue have brought up in the past and just have seen it brushed off. When trying to report and work on an investigation is makes no sense to create a ticket in our software development space when the issue would be normally in reported in Jira service desk where incident and problem are default issue types. This is much more accurate for anyone following an ITIL model for reporting incidents and problems. It’s all the more frustrating that IVM has the ability to query the issues on the Jira API we point it to and allow us to map the specific issue types.
Hi, we’ve been using IDR and IVM now for a few months and I think Insight is a great platform. I would like to know if there is a way to add custom cloud event sources using available APIs from other cloud security platforms? For instance, we have recently moved to Netskope web security for our cloud proxy and I’m wondering what the best way would be to add this as an event source when there is no out of the box integration from IDR?
Cheers,
Rich
@richard_burke - Thank you for the feedback! I checked with InsightIDR Product team and we do have plans to ship a Netskope event source and it’s in our backlog right now 
We will update you as soon as it is released!
Hope this is the right place to ask this question!
Are there any plans of creating a plugin for ManageEngine’s ADManager Plus?
Regards,
Brian
2 Likes
I’'m having the same exact issue. I cannot figure this one out. I added the “story” issue type to my jira service desk but same issue persists.
Also having this issue, in process of troubleshooting it with the support team, i’ll update here if I can get it resolved.