1. What is the nature and description of the request?

After upgrading from Ansible Automation Platform (AAP) 2.4 to AAP 2.5, the customer observed that the "Launched By (Username)" filter is no longer available in the Jobs UI.

In AAP 2.4, users could filter jobs directly from the UI using:

Login → Jobs → Search → Launched By (Username)

Although this filtering capability still exists at the API level in AAP 2.5 and AAP 2.6, it has been removed from the UI, resulting in an inconsistency between UI and API functionality.

The customer is requesting that this feature be restored in the UI, as it was available in AAP 2.4.

1. Why does the customer need this? (List the business requirements here)

• Users need to quickly identify and track jobs they previously launched without relying on API queries.
• The lack of a UI-based filter negatively impacts operational efficiency, especially in environments with a large number of jobs.
• Teams depend on this feature for auditing, troubleshooting, and accountability, particularly in shared or multi-user environments.
• The removal represents a functional regression from AAP 2.4, creating unexpected behavior after an upgrade.

1. How would you like to achieve this? (List the functional requirements here)

• Reintroduce the "Launched By (Username)" filter option in the Jobs UI search panel, consistent with AAP 2.4 behavior.
• Ensure the UI filter maps directly to the existing API filtering capability (to maintain consistency and avoid backend changes).
• The filter should support:

• • Username-based search

• • Partial or full username matching (if supported previously)

• The functionality should be available across AAP 2.5 and later versions, including 2.6.