Skip to:

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

ECS | "Effective location (item)" facet should be populated with locations of Holdings/Items from all member tenants regardless of user's permissions

Description

Overview: ECS | "Effective location (item)" (and "Holdings permanent location") facet should be populated with locations of Holdings/Items from all member tenants regardless of user's permissions

Steps to Reproduce:

  1. Log into ECS Poppy BF FOLIO environment as User with permissions to view instances only on Central tenant:
    Inventory: View instances, holdings, and items

  2. Go to "Inventory" app from Central tenant

  3. Find following shared "Instance" record: "cenin00000923634"

  4. Expand "Effective location (item)" facet

Expected Results: Locations from Member tenant in which user doesn't have permissions are displayed in the "Effective location (item)" facet ("Grad Students Law", "Serials).

Actual Results: Expanded "Effective location (item)" facet is empty.

Additional Information: same behavior is expected when user is on Member tenant.
URL: https://bugfest-poppy-consortium.int.aws.folio.org/inventory/view/9d435bc4-63a5-5273-9caf-f15f5bf18fb7?query=cenin00000923634&sort=title 

Interested parties: ,  

Environment

Potential Workaround

None

CSP Request Details

None

CSP Rejection Details

None

CSP Approved

None

Attachments

6
  • 07 Jun 2024, 02:54 PM
  • 10 May 2024, 10:19 AM
  • 07 May 2024, 01:05 PM
  • 07 May 2024, 01:05 PM
  • 11 Jan 2024, 12:00 PM
  • 11 Jan 2024, 12:00 PM

blocks

defines

has to be done before

relates to

Checklist

hide

TestRail: Results

Activity

Show:

Christine Schultz-RichertJune 10, 2024 at 7:57 PM

I agree with you Valery. We can proceed with further verification after the UI stories are completed. Closing this one as done.

Valery_PilkoJune 7, 2024 at 2:54 PM

Verified on ECS Sprint testing environment for Central tenant only - fixed.
User with permissions only on Central tenant can see locations from all members in “Effective location (item)” facet.
See attached screencast:

MSEARCH-660_verified_for_Central_tenant.webm

Following scenarios could be verified only after https://folio-org.atlassian.net/browse/UIIN-2901 and https://folio-org.atlassian.net/browse/UIPFI-153 are done:

  • User is on member tenant with permissions in Member and without permissions in Central tenant

  • User is on member tenant with permissions in Member and Central tenants

Hi - according to the described above, I recommend closing this back-end issue as “Done” and continuing verifications in the scope of specified UI tickets.

Pavlo SmahinMay 15, 2024 at 8:24 AM

Dev note: change logic of endpoint: allow to do call from member tenant, switch context to central in the module.

Christine Schultz-RichertMay 10, 2024 at 1:45 PM

Expected behavior is that the effective locations from all member tenants should be visible regardless of permissions. User should not need permissions in other member tenants to see other member tenant locations in the effective location facet.

Valery_PilkoMay 10, 2024 at 10:19 AM
Edited

Tested in the scope of https://folio-org.atlassian.net/browse/UIIN-2811 , results are following:
1) On central tenant user which doesn’t have permission in member tenants will see all locations from each member tenant in “Effective location (item)” facet. - works as expected
2) On member tenant user which doesn’t have permission in Central tenant will see only current Member tenant locations in “Effective location (item)” facet. - does it work as expected ?
3) On member tenant user which has permission in Central tenant and current Member tenant, but not in all other Member tenants, will see only current Member tenant locations in “Effective location (item)” facet. - does it work as expected ?
In description of current issue, we have a note: “Additional Information: same behavior is expected when user is on Member tenant.” Does it still valid requirement?
See attached screencast with details about 3rd issue:

MSEARCH-660_member_tenant_question.webm
Done

Details

Assignee

Reporter

Labels

Priority

Story Points

Sprint

Development Team

Spitfire

Parent

Release

Ramsons (R2 2024)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created January 11, 2024 at 11:59 AM
Updated June 21, 2024 at 10:35 AM
Resolved June 10, 2024 at 7:57 PM
TestRail: Cases
TestRail: Runs

Flag notifications