jweicai opened a new issue, #3418: URL: https://github.com/apache/incubator-streampark/issues/3418
### Search before asking - [X] I had searched in the [feature](https://github.com/apache/incubator-streampark/issues?q=is%3Aissue+label%3A%22Feature%22) and found no similar feature requirement. ### Description 1. I expect that on the application page, once I set some filter conditions or enter some query conditions, these conditions should be retained until I manually adjust them again. They should not disappear with a refresh or after opening to edit a task. 2. I expect the selection of display items to be savable (can be saved per user), not disappearing after a refresh as it does now. 3. I expect the width of each option to be adjustable and sortable, as the ApplicationName might be very long. 4. I expect Description to be displayed as an option. A lot of information cannot be known just by looking at the app_name, it can be seen through the remarks. Of course, only a part of it can be previewed. 5. I expect tags to support multiple selections, which can help us filter out a batch of tasks through multiple tags. 6. I expect the setting of records per page to be retained until I adjust it next time, not reverting to displaying 10 records after each refresh. 7. The login expiration time is about a day now, which is fine. But when it expires, can it check what the user is doing? I was writing a job task, and it was gone after a refresh, which is very uncomfortable. 8. I expect job alerts to be set according to status. For example, we do not expect alerts for the "CANCELED" status. 9. The logic of the sorting button is problematic. Now it is ascending order with one click, descending order with another click, and cancel with another click. It cannot directly select ascending or descending order. 10. I expect that double-clicking to copy the ApplicationName should only copy the application name. Now it will copy the preceding "SQL". 11. I expect to add an auto-incrementing applicationId before the ApplicationName, because having only the ApplicationName is inconvenient for communication and in some aspects. 12. The current issue with the Flinksql edit box: When the content in the edit box reaches the beginning or the end, no matter how you scroll the wheel, the page will not change. You have to move the mouse out of the edit box to scroll, which is not a good experience. I suggest making it automatically switch to the mode where the mouse is outside the edit box when it reaches the beginning or the end. 13. I expect to add a filter for the yarn queue, otherwise it's quite troublesome to find which tasks are in a yarn queue. ### Usage Scenario _No response_ ### Related issues _No response_ ### Are you willing to submit a PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
