We configured a Jira ticketing connection and set up multiple remediation projects to use it. Tickets are created in Jira when vulnerabilities are added to the remediation projects. When the vulnerabilities are remediated, the solutions are closed in insightVM but the Jira tickets are not being transitioned. Is this the expected behavior?
that was my experience as well.
Also, if the remediation project had multiple assets and some were resolved, the Jira ticket was not updated.
Hmm. I’m clearly missing something then. What’s the point of the integration if it isn’t going to automatically transition tickets? 
(Now we have two places to check and/or update.)
I turned it off exactly for that reason. I was hoping to use it to allow other teams who are not as familiar with IVM a way to address issues. I still use it in ICON when I just need a ticket to track time against, but not needed for two way communication.
Thanks @brandon_mcclure.
We’ll likely keep using it because it allows us to track the vulnerabilities in a more manageable way long term even though it does introduce some additional work to keep things in sync between systems. It also allows visibility into vulnerability tracking for folks who don’t need IVM access.
I’m not the only one, thank you 
I was experimenting with this and also thought since you have to map the Remediation Solution Status it would transition the issues automatically - or at least after you put them in “Awaiting Verification” and all affected assets are remediated.
Is that maybe something that can be done through InsightConnect?