History of "Run Now" extra command line arguments

[bbeaudreault]

For the Additional command line input (optional): box, it would be great if there was a history of what option combinations had been used in the past. I often find myself running the same commands or similar commands, but adding another procfile definition would be overkill.

This is similar to the use case of being able to ctrl-r to step through bash history, when we ran these commands on the servers.

[wsorenson]

You think this belongs in the Historical Tasks table?

Is it enough to be on the task page itself?

Does it need to be searchable (from where?)

[bbeaudreault]

I think this info should be available in a few ways:

1. Re-run an old task, from the Historical Tasks table. See Allow re-running an on-demand request from the "Historical Tasks" section #131. Ideally, you click a "Rerun now" button, which pops up the usual "Run now" dialog, but with the Additional command line input text box pre-populated.
2. It would be nice to just view this info in the Historical Tasks table as well. Even if it were in the JSON would be enough. Currently, to find an old argument list I used, I need to click in on each historical task, click JSON on the tasks page, and cmd+f for the right spot in the huge JSON.
3. The initial request of this issue, when you viewing the "Run now" dialogue. Currently the Additional command line input box is a simple text box. It would be great to make that an autocomplete/partial search box instead. In that way you could autocomplete some old parameters you've already used, or input a new parameter. (Even the usual browser autocomplete here would be better than nothing, but that doesn't work right now -- perhaps because the dialog is generated)

[tpetr]

implemented in #708