Traceability Report CSV export should respect quick filters

Problem Statement: Users exporting the Traceability Report to CSV currently receive a complete dataset regardless of any quick filters applied in the Jira UI. The output fails to match what the user has filtered on the screen, leading to confusion and extra manual effort to prune irrelevant records after export. This affects the Traceability Report CSV export feature in Xray. 

User friction:

• Users expect the CSV export to match the current filtered view.
• Today, the export always includes all traceability records, ignoring quick filters entirely.
• There is no way to export only the subset of issues relevant to the current analysis without manually post-processing the CSV.
• This is time-consuming and error-prone, particularly for large datasets where only a filtered slice is relevant. 

Steps to reproduce (workflow):

1. Open a Traceability Report in Xray.
2. Apply one or more quick filters to narrow down requirements/tests/results.
3. Export the report to CSV.
4. Observe that the CSV file contains all issues, not just those matching the applied filters.
5. Users must manually filter the CSV or re-export from an external tool to get the desired subset. 

IMPACT

What would improve if solved:

• CSV exports would align with user expectations and filtered views.
• Users could generate focused reports directly from Xray without extra tools or steps.
• Improves efficiency for reporting, audits, and external analysis workflows.

Impact on stakeholders:

• Test Managers, QA Engineers, Project Leads who rely on filtered exports for reporting and analytics.
• Occurs each time filtered traceability data must be shared with stakeholders or used in external tools.
• Frequent pain point for teams with large datasets or regulatory reporting needs.

Current workaround:

• Manually post-filter the exported CSV using spreadsheets or BI tools.
• Export full data and use filters externally, which is inefficient and risks discrepancies between on-screen and exported results.
• No built-in mechanism to restrict CSV exports based on quick filters today. 

CONTEXT & EXAMPLES:

Concrete example: A QA lead filters the traceability report to view tests covering high-risk requirements only. After applying those quick filters, the user expects the exported CSV to contain only those filtered results. Instead, the CSV contains every test-to-requirement relation in the project, forcing the lead to re-filter the file in Excel. 

Workaround risk: Manual post-processing of exports increases the risk of missing context or including irrelevant data in presentations or audits, particularly for regulated environments where exact filtered slices matter.