[UIORG-154] Can't create location Created: 08/Mar/19  Updated: 17/Apr/19  Resolved: 17/Apr/19

Status: Closed
Project: (inactive) ui-organization
Components: None
Affects versions: None
Fix versions: None

Type: Bug Priority: P2
Reporter: patty.wanninger Assignee: patty.wanninger
Resolution: Cannot Reproduce Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: JPEG File Screenshot_030819_020507_PM.jpg    
Issue links:
Blocks
is blocked by STCOM-489 AutoSuggest ref is not correctly crea... Closed
Sprint:
Development Team: Prokopovych

 Description   

Log in to Snapshot.stable
First, Create a service desk or make sure a service desk exists that relates to the location.
Then create a location.
Expected result: location created associated with the service desk

Actual behavior: When you try to save a location, you get the white-page error attached.



 Comments   
Comment by Cate Boerema (Inactive) [ 27/Mar/19 ]

Hi patty.wanninger I can't repro this in http://folio-snapshot.aws.indexdata.com but I am not sure I understand the repro steps.

When you say "make sure a service desk exists that relates to the location" what do you mean by "the location"?

When you say "Expected result: location created associated with the service desk", which service desk are you referring to?

A screencast might help clarify what you are seeing.

Thanks!

Comment by Zak Burke [ 29/Mar/19 ]

STCOM-489 Closed is the underlying cause; this ticket is the manifestation in the UI. This will automatically resolve when stripes-components is patched.

Comment by Cate Boerema (Inactive) [ 03/Apr/19 ]

patty.wanninger I can't repro this as described. I am able to create locations in snapshot-stable.

Zak seems to think this issue has the same underlying cause as UIORG-152 Closed . Maybe UIORG-152 Closed describes what you were doing when you saw this error?

Unless I have steps that repro, I won't be able to test this fix. I am assigning to you and putting this in draft for now. Please adjust repro steps and then mark Open and unassigned. Thanks much!

Comment by Zak Burke [ 03/Apr/19 ]

Revisiting this, I don't think it's related to STCOM-489 Closed .

Looking at the error message it appears the UI somehow got into a state where no primary service point is assigned, but I can't figure out how that happened. As Cate said, if you can provide repro steps that produce this result consistently, please update the description and reassign it.

Generated at Fri Feb 09 00:16:40 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.