Jobs window - Origin column shows incorrect origin

[JessePeden]

Version

5.0.7

Severity

Low

Environment

msi

Steps to Reproduce

If you add the Origin column to the Jobs window, the column shows incorrect values for scripts that are run as part of an Invoke-PSUScript command that is triggered by an API (Endpoint).

For example, I have an API that is configured with a single line of code that runs a script via Invoke-PSUScript, and the resulting job shows that it was "Manually Started".

Expected behavior

The column should reflect how the job was truly initiated.

Actual behavior

The column shows that the script was manually started, even when there was nothing manual about it.

Additional Environment data

No response

Screenshots/Animations

No response

[adamdriscoll]

We don't really have an indicator of where a script is coming from so calling Invoke-PSUScript is always considered manually run. Origin may have been a poor name choice for this column, but it does open the door the actually provide an origin.

I would even argue I would like to see which endpoint\app\script called the script for auditing purposes.

[JessePeden]

We don't really have an indicator of where a script is coming from so calling Invoke-PSUScript is always considered manually run. Origin may have been a poor name choice for this column, but it does open the door the actually provide an origin.

I would even argue I would like to see which endpoint\app\script called the script for auditing purposes.

Absolutely. That would be awesome.