Brijesh Khunt

> To test it I created a temporary branch from this one and merged the main implementation branch https://github.com/brijesh-elastic/kibana/tree/thehive_case_connector. Did I miss anything? Or should I wait until the first...

> Hi @brijesh-elastic, I see the connector _supportedFeatureIds_ is missing `CasesConnectorFeatureId` here > > https://github.com/elastic/kibana/blob/a98d141663a3a58bbe84c14af32dcb79f08ed4e2/x-pack/plugins/stack_connectors/server/connector_types/thehive/index.ts#L35-L39 > > Is it intentional? When I add the cases feature everything works well No,...

> @brijesh-elastic I've tested the connector, and everything is working fine. The only thing I miss is the case's `status` property is not synced. I noticed it is not in...

@semd, Regarding the [comment ](https://github.com/elastic/kibana/pull/207255#issuecomment-2916001279), to address the issue of invalid JSON, we can modify the template. During implementation, we identified that [threat.technique.id](https://www.elastic.co/docs/reference/ecs/ecs-threat#field-threat-technique-id) is an array, which requires repeating the...

Discussed with @cnasikas and @semd, decided to [remove](https://github.com/elastic/kibana/pull/207255/commits/5eac0f533319d6d7318e2eaf7e5a42598a4c5926) custom templates feature for this release.

> Could you please add an integration test in `x-pack/platform/test/alerting_api_integration/security_and_spaces/group2/tests/actions/connector_types/thehive.ts` in your upcoming PR where you unhide the fields in the UI? Yes, we'll add.