add parent segments list to 'Used By' status of segments

[bcb37]

• Adds an array of all segments that are parent segments of any of the segments corresponding to the supplied segment IDs to the return value from the backend for any segments 'with status' call
• Uses that data in the frontend to determine 'Used' status and 'Used By' data
• Display of parent segment info in the 'Used By' tab follows that of experiments and feature flags, including a link to the parent segment's details page; 'Status' defaults to 'Active' for all segments.

[Copilot]

Pull Request Overview

This PR extends the segment “Used By” status to include parent segments in both backend and frontend.

• Backend: fetches parent segments in the getSegmentStatus call and exposes a new repository method.
• Frontend: wires allParentSegments through actions, reducers, selectors, service, and templates; updates UI to display segments in the “Used By” tab.
• UI/UX: updates i18n subtitle and enhances tab component to support programmatic tab selection.

Reviewed Changes

Copilot reviewed 17 out of 17 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
frontend/projects/upgrade/src/assets/i18n/en.json	Updated “Used By” subtitle to mention segments
frontend/projects/upgrade/src/app/shared-standalone-component-lib/components/common-tabbed-section-card-footer/common-tabbed-section-card-footer.component.ts	Added @Input() selectedIndex
frontend/projects/upgrade/src/app/shared-standalone-component-lib/components/common-tabbed-section-card-footer/common-tabbed-section-card-footer.component.html	Bound [(selectedIndex)] for two-way tab control
frontend/projects/upgrade/src/app/features/dashboard/segments/pages/segment-details-page/.../segment-overview-details-footer.component.ts	Added tab reset on init/changes and selectedIndex state
frontend/projects/upgrade/src/app/features/dashboard/segments/pages/segment-details-page/.../segment-overview-details-footer.component.html	Passed selectedIndex into common tab footer
frontend/projects/upgrade/src/app/core/segments/store/segments.selectors.ts	Introduced selectParentSegments and processParentSegments hook
frontend/projects/upgrade/src/app/core/segments/store/segments.reducer.ts	Added allParentSegments to state and reducer cases
frontend/projects/upgrade/src/app/core/segments/store/segments.reducer.spec.ts	Updated reducer tests to include allParentSegments
frontend/projects/upgrade/src/app/core/segments/store/segments.model.ts	Added USED_BY_TYPE.SEGMENT and allParentSegments to model
frontend/projects/upgrade/src/app/core/segments/store/segments.effects.ts	Populated allParentSegments in fetch effects
frontend/projects/upgrade/src/app/core/segments/store/segments.effects.spec.ts	Mocked allParentSegments in effects tests
frontend/projects/upgrade/src/app/core/segments/store/segments.actions.ts	Extended actions to carry allParentSegments payload
frontend/projects/upgrade/src/app/core/segments/segments.service.ts	Exposed allParentSegments$ selector
frontend/projects/upgrade/src/app/core/local-storage/local-storage.service.ts	Persisted allParentSegments in local snapshot
backend/packages/Upgrade/test/unit/services/SegmentService.test.ts	Added mocks and expectations for getAllParentSegments
backend/packages/Upgrade/src/api/services/SegmentService.ts	Implemented getParentSegments and integrated into getSegmentStatus
backend/packages/Upgrade/src/api/repositories/SegmentRepository.ts	New getAllParentSegments repository method

Comments suppressed due to low confidence (2)

frontend/projects/upgrade/src/assets/i18n/en.json:541

• The no-data message still only mentions experiments and feature flags. It should also mention segments to match the updated subtitle.

  "segments.details.used-by.card.no-data-row.text": "This segment is currently not being used by any experiments or feature flags.",

frontend/projects/upgrade/src/app/core/segments/store/segments.selectors.ts:221

• New parent-segment processing logic isn’t covered by existing selector tests. Add unit tests for selectSegmentUsageData to validate parent segments appear correctly.

    processParentSegments(parentSegments, segment.id, usedByMap);

[zackcl]

What if segment "A" is used by segment "B", and segment "B" is used by feature flag "C"?

Should we display both segment "B" and feature flag "C" in the "Used By" table for segment "A"? Or just segment "B" in this case?

I feel like it's better to display only the direct (one-level higher) parent—just segment "B" with its actual status (instead of "Active").

I believe we originally decided to display only the top-level non-segment parents (experiments or feature flags) in the "Used By" table, but it might be more helpful to show only direct parents so users know exactly where to remove the segment.

Maybe we should bring this up in the meeting.

[bcb37]

What if segment "A" is used by segment "B", and segment "B" is used by feature flag "C"?

Should we display both segment "B" and feature flag "C" in the "Used By" table for segment "A"? Or just segment "B" in this case?

I feel like it's better to display only the direct (one-level higher) parent—just segment "B" with its actual status (instead of "Active").

I believe we originally decided to display only the top-level non-segment parents (experiments or feature flags) in the "Used By" table, but it might be more helpful to show only direct parents so users know exactly where to remove the segment.

Maybe we should bring this up in the meeting.

@zackcl I'm not sure I understand the question. We are still only showing direct parents - just one level - in the 'Used By' list, as specified. Can you give a specific example of what you're describing, maybe with a screenshot?

[zackcl]

@bcb37 My apologies — I thought we were also displaying top-level parents, but it appears we are indeed showing only the direct parents, as I just tested it. One suggestion I’d like to make is to display the actual status (Used / Unused / Excluded) of each parent segment instead of just "Active." Would this be possible?