Open EricDavisX opened 2 years ago
Pinging @elastic/response-ops (Team:ResponseOps)
Pinging @elastic/kibana-docs (Team:Docs)
I think assuming that there are no other underlying changes in functionality that require us to keep the instructions and interfaces split off in parallel, that it makes sense to update the docs and UI to the new name.
Hi! I think before updating the name we should test our integration to the new version. With the new naming, the users may assume that our integration works with the latest version. Though we do not specify until which version our integration is tested.
ok - let's put this on hold and have a separate testing discussion off-line to work it. Thanks for the quick communication.
@cnasikas updates me that he has done incremental testing over all recent versions in upgrading our test environment. He sees no problems, and I can confirm our long-running QA 'rules' environment is posting issues to the test env which is now running IBM QRadar Soar v45.2.37.
I had understood this was possibly waiting on PM due to contractual things like getting the latest logo into our code so we're still on hold. But, it is great news to see that it is working now and just a formality to have the name / icon updated.
Kibana version: 8.4-SNAPSHOT
Describe the bug: We should update our Docs and some in-product references to IBM Resilient connector. Resilient changed names to 'IBM Security QRadar SOAR' in December 2021
Steps to reproduce: Referencing: https://www.ibm.com/support/pages/ibm-security-qradar-soar-release-changelog
Any additional context: Caught between a bug and an enhancement... I feel we should try to keep up with Industry name changes, we'd want them to if / when we were to change.
Definitely worth discussion and we should get product to sign off before working it.