Improve Global Configuration History Graph Usability with Filtering and Detailed Configuration Views

Context:

Large production projects generate a high volume of Global Configuration changes. The History Graph quickly becomes crowded and difficult to use.

Problem:

The History Graph is not filterable, making it hard to analyze configuration evolution when hundreds of configurations are displayed. Users also cannot easily access detailed information about a selected configuration; they can only access easily  modification (added / moved components etc).

Impact:

The graph becomes impractical for production environments, reducing its value for analysis, troubleshooting, and audits.

Goal of the Idea:

Make the History Graph usable on large-scale projects by enabling filtering and detailed configuration inspection.

Why is it Useful?:

• Improves usability and navigation
• reduces analysis time
• Helps users focus on relevant configurations
• Increases adoption of the History Graph feature.

How Should it Work?:

• Add filters (stream, release, date range, configuration name, owner)
• Allow users to click/expand a configuration and view its details
• Provide a detailed view similar to the existing component-change view (added, removed, moved, modified components) => being able to configure size card content (like in EWM task board) to be able to have not the complete list of modification one by one but the result compare to the original (similar to redlining).
• Support collapsing and expanding sections of the graph to reduce clutter.