Collector UI State Doesn't Reset about attacksurfaceanalyzer

[gfs]

I'm not sure I'm going to make any changes here.

The behavior shown above is exactly what they'd see if they stayed on the page without navigating away.

The difficulty is that if the user navigates away and comes back and the collectors are actually still running we need to show the correct status (and not allow them to start a new run).

The alternate behavior would be that they navigate back and, if the collectors are still running we still show that status, and if not it would just show the empty collect page. However, I think this creates a potential point of confusion for the user, as they may not be sure that the run they started before navigating away actually completed.

[guyacosta]

I see. Then my suggestion is to keep the ScanID after the collection completes as well so that it is more clear and when of if the user wants to start a new one they will change the ScanID or be prompted to if they haven't for uniqueness etc. Currently we have state but no scan id associated in the UI. This is actually a better UX as they then know for certain that the last request was completed rather than emptying all state and is likely much less work to do.

[gfs]

If we keep the old scan id in the box it breaks the flow of automatically using the timestamps, but I think we can find a way to accomplish the same here. What about indicating what run the status applies to in the status box? We can redesign that box a bit anyway to make it more of its own UI element.

[gfs]

Here's the new UX