When using the JOBS view provided by the Zowe extension for VSC, it would be useful to be able to filter by jobid. For example zowe zos-jobs list jobs returns a list of jobids so it would be useful to copy a jobid from that list and find it quickly using the extension.
Perhaps the default view should show the job id by default in place of the job name.
When you submit a job, you're presented the jobid although you view it by jobname:

Maybe the presentation of the jobs could be similar to z/OS explorer jobs view?
It would be beneficial to be able to see both the job name and the job id, especially in cases where you submit the same job multiple times.
@MikeBauerCA You can see the Job Id if you hover on a particular job

The aim with showing either the RC or the ACTIVE status was that if the same job had been submitted multiple times then the latest one would be easy to find.
work in conjunction with #118
@markcocker There is now a magnifying glass option to specify a more comprehensive search that includes owner, prefix or jobId. That option also has access to search history. The intention was to get something out there (whilst we are still in development mode) and ask for feedback. VSCode supports the creation of create simple dialogs (an entry field or quick pick) and to get a combination of items the only option is to link them. So it would be good to get your perspective.
@Colin-Stone Thanks - initial feedback from trying it out:
Thanks @markcocker. I created https://github.com/zowe/vscode-extension-for-zowe/issues/263 to cover points to 3.
The answer to 4 is that you can't. I've implemented a set with a capacity of 5 unique items each time you create a new item or select an item from the set it gets pushed to the front. If you add a new item to the set and the set exceeds 5 the last one drops off. So for example if you had a specific jobId filter set up and you have deleted that job, it would remain as an option in the filter list until you added enough additional filters for it to drop off the end of the list from lack of use.
Hope that makes sense. It seemed a reasonable solution I could apply consistently to filters on all three views