v-kkhuang opened a new issue, #5395:
URL: https://github.com/apache/linkis/issues/5395

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/linkis/issues) and found no similar feature 
requirement.
   
   ### Problem Description
   
   Is your feature request related to a problem? Please describe.
   
   Currently, the global history management console does not display engine 
version information, making it difficult for users to track and identify which 
engine version was used for specific task executions.
   
   ### Description
   
   A short description of your feature
   
   Add engine version display functionality to the global history management 
console, allowing users to view the engine version associated with each 
historical task record.
   
   ### Use case
   
   Describe the use case of your feature request and the solution you'd like.
   
   When users review historical task execution records in the management 
console, they need to know which engine version was used for better 
troubleshooting and analysis. This feature enhances traceability and helps 
users understand their task execution context.
   
   ### Solutions
   
   Describe alternatives you've considered.
   
   - Add engine version field to the global history display
   - Update frontend components to render engine version information
   - Add documentation for the new feature
   
   ### Anything else
   
   Additional context or screenshots about the feature request.
   
   This is part of the dev-1.18.0-webank development plan.
   
   ### Are you willing to submit a PR?
   
   - [x] Yes I am willing to submit a PR!


-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to