Closed roamye closed 1 week ago
Discussion from ticket forming... Should revert to the last previous search tab state.
I have discovered some interesting functionality. Outlined below are 3 scenarios and their current and expected behavior.
NOTE: All scenarios should take place in the Objects search.
Scenario 1:
(-)
Expected behavior:Scenario 2:
Anywhere
from the single field dropdownAnywhere
(-)
Expected behavior:Scenario 3:
Dimension
from the single field dropdownless than
from the comparator dropdownDimension
(-)
Expected behavior:@jffcamp @roamye @dcheather @prowns Please advise on how the frontend should behave in the above scenarios and if anything is incorrect. I'm bringing this to everyone's attention since it is impacting how I should move forward on this issue.
@kamerynB - I agree with 1 & 2. For 3 can the trip back to simple search provide a message to alert the user that x terms will be dropped because it isn't available with Simple Search?
@kamerynB -
Scenario 1: the expected behavior is: The estimates should show the previous estimates state from the simple search. Question - does this imply the previous estimates across all tabs or just the tab which it was previously on? (ex: displaying the previous estimate on the Object tab only)
Scenario 2: I have the same question from scenario 1, but I am assuming in scenario 2 we would only want to display the previous estimate of the tab the AS was submitted on.
Scenario 3: I think this ok with an error message somewhere to indicate this will happen.
We can continue discussing later in a meeting.
From Meeting 9/18: *behavior reflected against all test environments
When a user switches back to simple search the FE is making a new search for each tab as it recognizes it as a simple search. Q: We tell the user that when they switch back to simple search all the info will be lost. As a user we would hope to not see the result.
In either scenario (2&3) should we result to its default simple search that they had before? or do we maintain what they had for their advanced search and make sure the results do not come with the error? -> switching to a new tab will show a new blank simple search when switching from AS back to SS. -> error message for going back to simple search needs to be updated. As the message is not clear as you are not losing all input.
Next Steps:
@roamye @jffcamp @prowns
Scenarios 2 & 3 Steps and Expected Behavior:
Add Row
Dimension
from the single field dropdownDimension
Add Row
Anywhere
from the single field dropdownAnywhere
(-)
)
I don't love the blank screen, but if that's the best solution, I'm ok with it. What will the pop-up warning say? Could there also be a message here in the white space inviting users to enter a new search. It's pretty hostile.
@kamerynB - Might be out of scope, but to keep consistency, if the user goes back to an AS (from the blank screen) should the AS also be blank? Currently it still shows the AS query used in objects in the AS Works tab.
Based on our previous discussion the mockup looks good. But @prowns does bring up a good point.
I am ok with this but agree that if we can add a message to the blank grey screen that would be better. If that is problematic I'm fine with that being a standalone ticket.
@roamye @jffcamp @prowns I can address all the concerns. This ticket is more involved and will take some minor refactoring I believe. I will be pushing it to the next milestone.
IT Team Meeting 10/4:
Approved by UAT
Looks good in PROD. Closing.
Problem Description: When a user creates a simple search and goes to Advanced Search the number of records displays correctly within its tab. However if you switch to/go back to simple search this number no longer displays. Instead it displays the tab name + (-). For example:
Objects (-)
Expected Behavior/Solution: When a user switches to simple search from advanced search, the estimates should reflect the advanced search estimates as the other tabs should not have results. When a user then navigates to a different tab, an information alert will display a message telling the user to perform a new simple search to search under the current tab.
Requirements:
Needed for promotion: If an item on the list is not needed, it should be crossed off but not removed.
UAT/LUX Examples: *AS and AS to SS examples will have matching tab counts once deployed.
Dependencies/Blocks:
Related Github Issues:
Related links:
Wireframe/Mockup: Current:
Updated: