Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

"Current page unstable" errors due to missing elements.

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.

CSP Request Details

None

CSP Rejection Details

None

Potential Workaround

None

Attachments

1
  • 02 Aug 2019, 05:57 PM

relates to

Checklist

hide

TestRail: Results

Activity

Show:

Khalilah Gambrell January 30, 2020 at 4:02 PM

, closing this issue.

Cate Boerema January 30, 2020 at 9:30 AM

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 https://folio-org.atlassian.net/browse/MODUSERS-139#icft=MODUSERS-139.

Can you please close this if you agree?

Khalilah Gambrell August 6, 2019 at 3:06 PM

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

  • Address Type component needs to be reviewed

  • Need a better UI error screen

Cate Boerema August 5, 2019 at 10:28 AM

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 https://folio-org.atlassian.net/browse/UIREQ-308#icft=UIREQ-308

patty.wanninger August 2, 2019 at 5:57 PM

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

Duplicate

Details

Assignee

Reporter

Labels

Priority

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created August 2, 2019 at 5:55 PM
Updated June 3, 2020 at 4:40 PM
Resolved January 30, 2020 at 4:02 PM
TestRail: Cases
TestRail: Runs

Flag notifications