[Feature Request]: Test runs to not open in a new tab/window

[nickdollimount]

Is there an existing feature request for this?

• I have searched the existing issues

What is your feature request?

Currently when executing a test run of an event, it opens the running job in a new tab/window. I'm not sure if this is by design but I guess it's bothering me enough to want to ask it not to do that 😄.

Code of Conduct

• I agree to follow this project's Code of Conduct

[jhuckaby]

LOL 😝

Sorry about that, and I can probably make this configurable via a user preference, but first, please let me explain why I have tests pop open a new tab...

When you test an event via the "Test..." button, it actually runs the event in its current unsaved state. Meaning, you can make changes -- any changes you like -- and then you can test those changes without saving.

When the test dialog launches a job, it "overrides" all the saved event settings with your current changes from the editor, saved or unsaved, and then launches that as a custom job.

For this reason, I have it spawn a new browser tab, so you don't "lose" your unsaved changes by having the main tab navigate away from the current event editor page.

For e.g. you can actually go in and edit the script (if you are using the Shell or Powershell Plugins), and then actually test (run) those script changes without saving over the event. Try out a new action? Test it without saving! It's a really great way to test out new changes without committing! And not messing up scheduled jobs (which will of course use the last saved version).

Cool, right? But this nifty trick really only works if it launches a new tab. Otherwise, all those changes you made are basically "lost" as the page navigates away to the job detail screen.

Note

Side-Note: Many, many, many versions ago (like before the beta), I had it auto-save your event changes into a "draft" if you left the page without saving, and then it restored them when you revisited the page. But this confused SO many people, I had to rip it out. And it was a huge amount of complex code.

Anyway, I can probably add a user preference for this, like a "Launch Tests in Current Window" checkbox, but if anyone checks it, it will basically kill the "test unsaved changes" feature 😞

[nickdollimount]

I didn't actually realize the test button was running unsaved changes... I've been saving my changes to then click the Test button! 😭😆

That certainly explains the 'why' and makes total sense. Another example of me just not knowing how things work 😄.