Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RFE] Missing indication that analysis with given targets was successfull #2012

Open
1 task done
rszwajko opened this issue Jul 12, 2024 · 2 comments
Open
1 task done
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/normal Higher priority than priority/minor. Nice to have. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@rszwajko
Copy link
Collaborator

Is there an existing issue for this?

  • I have searched the existing issues

Konveyor version

0.5beta

Priority

Undefined (Default)

Current Behavior

Analysis of OpenMRS app using target Spring Boot on Red Hat Runtimes seems to return no issues. This (positive) result is not clearly presented to the user and looks similar to failed analysis (i.e. #111 ). It's also not clear (without looking into the details yaml) what config was used for the last analysis.

Full log:
no_issues_found.yaml.txt

UI:
Screenshot from 2024-07-12 17-18-33

image

Expected Behavior

Information in the app details:

  1. list of targets that the project was checked against
  2. configuration used (basically a read only information from the wizard)
  3. issues summary i.e. " X critical, Y minor" or "Congratulations! No issues were found "

How Reproducible

Always (Default)

Steps To Reproduce

Analysis of OpenMRS app using target Spring Boot on Red Hat Runtimes

Environment

No response

Anything else?

No response

@rszwajko rszwajko added kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jul 12, 2024
@konveyor-ci-bot
Copy link

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.

@konveyor-ci-bot konveyor-ci-bot bot added the needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. label Jul 12, 2024
@github-project-automation github-project-automation bot moved this to 🆕 New in Planning Jul 12, 2024
@sjd78 sjd78 added triage/accepted Indicates an issue or PR is ready to be actively worked on. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/normal Higher priority than priority/minor. Nice to have. and removed kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates an issue or PR lacks a `priority/foo` label and requires one. labels Jul 18, 2024
@sjd78 sjd78 moved this from 🆕 New to 📋 Backlog in Planning Jul 18, 2024
@sjd78 sjd78 changed the title [BUG] Missing indication that analysis with given targets was successfull [RFE] Missing indication that analysis with given targets was successfull Aug 21, 2024
@DvoraShechter1
Copy link
Contributor

I'm working on this issue. Please assign it to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. priority/normal Higher priority than priority/minor. Nice to have. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Status: 📋 Backlog
Development

No branches or pull requests

3 participants