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

[MTV-1801] [RFE] Non informative message #1462

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jpuzz0
Copy link
Contributor

@jpuzz0 jpuzz0 commented Feb 6, 2025

📝 Links

https://issues.redhat.com/browse/MTV-1801

📝 Description

Improve message to point users to the "Mappings" tab, indicating editing is required to solve specific Critical condition type error responses for plans.

The JIRA issue suggests including more information in the alert, and we can figure out which storage and network maps are missing, but that information is more readily available in the Mappings tab, and it seems like that is the best place to call those missing mappings out. How we do that exactly is a question for UXD, which can be a separate enhancement follow-up to this solution.

🎥 Demo

Screen.Recording.2025-02-05.at.2.47.57.PM.mov

Signed-off-by: Jeff Puzzo <jpuzzo@redhat.com>
Copy link

sonarqubecloud bot commented Feb 6, 2025

@codecov-commenter
Copy link

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 36.32%. Comparing base (13484d0) to head (af24f7b).
Report is 218 commits behind head on main.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1462      +/-   ##
==========================================
- Coverage   36.81%   36.32%   -0.50%     
==========================================
  Files         158      156       -2     
  Lines        2548     2522      -26     
  Branches      599      588      -11     
==========================================
- Hits          938      916      -22     
- Misses       1428     1601     +173     
+ Partials      182        5     -177     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@jpuzz0 jpuzz0 added the bug Categorizes issue or PR as related to a bug. label Feb 6, 2025
@metalice
Copy link
Collaborator

@jpuzz0 can tell the user exactly which mapping is missing? like SC name, network name

@jpuzz0
Copy link
Contributor Author

jpuzz0 commented Feb 10, 2025

@jpuzz0 can tell the user exactly which mapping is missing? like SC name, network name

@metalice
Yes, but this gets into design territory as there could be a large number of missing items in multiple categories, as mentioned, network mappings, along with what this story only called out, storage mappings.

So to display all of that information within an Alert might not be the way to go, especially since there needs to be a couple additional API requests to even determine those names. I think pointing users to the page where they can edit, where these requests are already being made, and using form errors would be more efficient and I can talk to the UXD folks about this more as a follow-up. (briefly mentioned this in the description of the PR)

@metalice
Copy link
Collaborator

@jpuzz0 can tell the user exactly which mapping is missing? like SC name, network name

@metalice Yes, but this gets into design territory as there could be a large number of missing items in multiple categories, as mentioned, network mappings, along with what this story only called out, storage mappings.

So to display all of that information within an Alert might not be the way to go, especially since there needs to be a couple additional API requests to even determine those names. I think pointing users to the page where they can edit, where these requests are already being made, and using form errors would be more efficient and I can talk to the UXD folks about this more as a follow-up. (briefly mentioned this in the description of the PR)

Can we add collapse into the alert? so it will be closed and hidden by default and expand if a user want to know more info?

@heyethankim
Copy link
Collaborator

heyethankim commented Feb 11, 2025

The alert box should focus on what happened and why. The recovery process, including more details, should take place on the target page, which is the "Mappings" page.

@metalice This is the general rule. Since the plan can’t run due to this issue, don't users want to diagnose the problem within the page?

@heyethankim
Copy link
Collaborator

@metalice, thank you so much for sharing the CNV example. One thing we agreed on is to preserve the target page in the alert message, which is the Mappings page. Now it is really about determining if there’s any additional information we need to include in the alert message.

Could you help us to figure that out?

Just reviewed the Mappings page. There is a transition when users click on “Edit mappings.” I am wondering if, upon clicking “mappings” from the alert message, we can allow users to access the page to edit mappings directly, rather than adding more instructions. If we do, it is really just about adding or removing, correct?

I think we definitely need help from @wolfeallison with the inline alert messaging.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants