[Security Solution] Inconsistent conflict state messaging in Rule Upgrade flyout

[pborgonovi]

Epic: #174168

Summary

Describe the bug:
When the Related Integrations field is removed in a customized rule and the rule is opened in the Update Flyout, inconsistent conflict state messages are displayed. Specifically:

• The top red banner shows an “Unsolved conflict” message, indicating user action is required.
• Simultaneously, the “Related Integrations” field displays a “Solved conflict” message in the Diff view, even though the Final update column remains empty.

Kibana/Elasticsearch Stack version:
8.x

Current branch: 8.x  
Latest commit: f38870d176a - [8.x] Swaps template literals for sprintf style interpolation (#200634) (#200737)  
Remote tracking: origin/8.x  
Status relative to remote: up to date (no pending commits)  

Pre requisites:

1. Old rules package is installed
2. A rule containing related integrations is available (e.g: GitHub Repo Created)

Steps to reproduce:

1. Open a rule with existing Related Integrations in the rule settings
2. Edit rule and remove all related integrations and save the changes
3. Update rules package to the latest
4. Open Rules Updates page
5. Open the Update Flyout for the rule.

Current behavior:

• The red banner at the top of the flyout displays “Unsolved conflict” messaging.
• The Related Integrations field in the Diff view displays a “Solved conflict” message.
• The Final update column for the Related Integrations field is empty, despite being marked as solved.

Expected behavior:

Conflict Messaging Consistency:

• If the field has no proposed resolution, only the “Unsolved conflict” message should appear.

• The “Solved conflict” message should display only when a valid proposal exists in the Final update column.

• If the system marks the field as “Solved conflict”, the Final update column must include a valid proposal.

• If no proposal is available, the field should remain marked as an “Unsolved conflict.”

No Simultaneous Messages:

• “Unsolved conflict” and “Solved conflict” messages should never appear together.

Screenshots (if relevant):

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[elasticmachine]

Pinging @elastic/security-detection-rule-management (Team:Detection Rule Management)

[elasticmachine]

Pinging @elastic/security-detections-response (Team:Detections and Resp)

[banderror]

@pborgonovi Yes, this UI is very confusing and we discussed this during the demo made by @maximpn at the product meeting.

We'll keep the bug: we discussed with @maximpn @nikitaindik and @xcrzx that we should prioritize fixing rule upgrade blockers and UX issues such as this one in the next 1 or 2 weeks.

[banderror]

@pborgonovi This one should have been fixed by @maximpn in #201501

[pborgonovi]

Retested with latest changes and fix looks good:

Without Elastic updates:

With Elastic updates causing unsolved conflict: