[FOLIO-2206] "Current page unstable" errors due to missing elements. Created: 02/Aug/19  Updated: 03/Jun/20  Resolved: 30/Jan/20

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: P3
Reporter: patty.wanninger Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: bugfest_q3.1.2019
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: JPEG File Screenshot_072919_031655_PM.jpg    
Issue links:
Relates
relates to STCOM-336 Catastrophic Error Messaging UI Closed
relates to MODUSERS-139 Make Address type required Blocked
Sprint:

 Description   

Discussed this with FSE team - this is likely a STRIPES problems - need to decide if missing info is required, if not, handle error more elegantly.

Put any examples of the unstable page error in comments.



 Comments   
Comment by patty.wanninger [ 02/Aug/19 ]

REQUESTS: In the bugfest environment, try to place a new request. Search the requester. Select a requester and press return. Error occurs.

Comment by Cate Boerema (Inactive) [ 05/Aug/19 ]

Patty's intention is to populate this bug with all the current page unstable errors she sees. At this point there is only one (related to missing address type) which is already covered by MODUSERS-139 Blocked

Comment by Khalilah Gambrell [ 06/Aug/19 ]

8/6/2019 Stripes Force Grooming (need to create two stories)

  • Address Type component needs to be reviewed
  • Need a better UI error screen
Comment by Cate Boerema (Inactive) [ 30/Jan/20 ]

Khalilah Gambrell this bug is not assigned to a dev team so it caught my attention. I am tempted to close it, as there is very little info here. I think the issue with Requests is related to MODUSERS-139 Blocked .

Can you please close this if you agree?

Comment by Khalilah Gambrell [ 30/Jan/20 ]

Cate Boerema, closing this issue.

Generated at Thu Feb 08 23:18:59 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.