Closed kthatipally closed 1 month ago
We mentioned the idea of using the word "insights" instead of "issues" for these information rules
Hey folks, we have started an enhancement around this: https://github.com/konveyor/enhancements/pull/174 Feel free to comment with your inputs.
This issue is currently awaiting triage.
If contributors determine this is a relevant issue, they will accept it by applying the triage/accepted
label and provide further guidance.
The triage/accepted
label can be added by org members.
Hello,
We hank you for the request, I do wonder if the insights enhancement https://github.com/konveyor/enhancements/pull/174 covers the use case.
Can you give that a review and see if we are missing something in that enhancement?
Currently, static-reports generated by Kantra utilizes tags to provide basic information utilizing our information rules. While these tags offer some insight, they often fall short in conveying comprehensive details about input applications. We are requesting to enhance the existing tagged rules by providing additional details beyond tags to provide deeper understanding of the input applications. These supplementary fields would offer users more comprehensive insights, to empower users with greater clarity in discovering the input applications. This is particularly useful when running the analysis on the old legacy applications.