Feature Overview (aka. Goal Summary)

When debugging failed runs it would be very beneficial to be able to see who triggered the workflow, both on the "workflow instance" page and also as a column in the "workflow runs" table (see screenshots).

It would also be great if we could search/filter the workflow instances in the table by the user who triggered them and/or by the workflow name.

Goals (aka. expected user outcomes)

View the user who triggered the workflow

Search the workflow instances based on owner/run by

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order
to be considered complete. If the feature spans across releases then good
to have scope for each release with acceptance criteria. Be sure to
include nonfunctional requirements such as security, reliability,
performance, maintainability, scalability, usability, etc.

<enter general Feature acceptance here>

Out of Scope (Optional)

High-level list of items that are out of scope.

<your text here>

Customer Considerations (Optional)

Provide any additional customer-specific considerations that must be made
when designing and delivering the Feature. Initial completion during
Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that
documentation will meet customer needs. If the feature extends existing
functionality, provide a link to its current documentation.

<your text here>