Feature: Creator History & Metadata for Tests/Campaigns

[CurtGrizzle]

I am often frustrated when managing or reviewing the dashboard which contains dozens of active Tests and Campaigns. Currently, there is no easy way to identify who initiated a specific test or when it was exactly created.

When I need further clarification on a test's parameters or strategy, I am unable to identify the original owner. This leads to inefficient workflows where I must message the entire team to find the initiator, rather than addressing the specific individual directly. As the volume of tests scales, this lack of visibility creates accountability gaps and slows down decision-making.

I would like to see Creator Metadata exposed in the UI for both Tests and Campaigns. Specifically:
-Dashboard List View: Add a column or indicator for "Created By" (User Name) and "Created On" (Date/Time).
-Details View: When clicking into a specific Test or Campaign, the header or metadata section should clearly state the initiator's username and the timestamp of creation.

Ideally, this data would be sortable or filterable, allowing me to quickly see all campaigns created by a specific team member or within a specific date range.

Alternatives considered:
-Manual Naming Conventions: We have considered mandating that users add their initials to the Test/Campaign title (e.g., "Test A - [JD]"), but this relies on manual adherence, eats up character limits, and is prone to human error.
-External Documentation: Tracking test ownership in a separate spreadsheet or project management tool (Jira), but this creates context switching and the data often falls out of sync with the actual platform.
-Team Broadcasts: Currently, we have to ask in meetings/Slack/teams channels "Who made this test?", which is noisy and inefficient.

Additional context:
-In a collaborative environment with high-velocity testing, "mystery" campaigns can be dangerous if we need to quickly pause or edit a test and don't know the original context.

Example: A "Created By" column next to the "Status" column would fit naturally into the current layout.
Impact: This feature would significantly reduce time-to-resolution for questions regarding specific campaign settings.

[SRAPSpencer]

I appreciate the detailed feature request. I think it would be helpful to have a better idea of how your testing workflow is structured. Traditionally VECTR use looks like this,

1. Team plans assessment by creating an Assessment Template from the Library or MarketMaker
2. Team creates Assessment using said template, setting dates for execution and tools in the environment
3. Team executes test plan populating red/blue results
4. Team moves into reporting phase, assessment complete

It sounds like you're creating an assessment ad-hoc, populating it with many campaigns doing much more rapid higher volume testing. I'd love to hear more about your workflow and use case(sounds much more Red Team driven?). Feel free to email us if you'd like to discuss. vectr@sra.io

Just as a heads up, while we don't discourage this workflow we have multiple reports based on comparing running a specific planned assessment in Q1 and again in Q2 and comparing these two identical test plans run over run. In your use case, these reports aren't likely to function as intended.