Issues

Select view

Select search mode

 
18 of 18

ECS: Use useTenantKy instead of useOkapiKy for Poppy

Done

Description

As far as useOkapiKy from stripes-core with the support of a custom tenant was introduced in Quesnelia it is necessary to use a custom useTenantKy hook to send requests in a proper context.

 

Critical service patch details

  1. Describe issue impact on business - The work described in this ticket is required to complete UIIN-2780, which has already been approved for inclusion on Poppy CSP 5. This is ECS-specific work to ensure that Consortial Holdings is accessible to all users regardless of affiliations.

  2. What institutions are affected? (field “Affected Institutions” in Jira to be populated) - All ECS.

  3. What is the workaround if exists? Only workaround would be to assign Affiliations for all Member Tenants to all Users, which would be cumbersome and tedious to maintain.

  4. What areas will be impacted by fix (i.e. what areas need to be retested) - ui-inventory; “Consortial Holdings” accordion.

  5. Brief explanation of technical implementation and the level of effort (in workdays) and technical risk (low/medium/high). - Update Poppy to use useTenantKy instead of useOkapiKy for hook to send requests in a proper context. Low effort.

  6. Brief explanation of testing required and level of effort (in workdays). Provide test plan agreed with by QA Manager and PO.  - Low effort.

  7. What is the roll back plan in case the fix does not work? Revert to previous version.

CSP Request Details

Requested CSP Approval via slack on 5/3/2024

CSP Rejection Details

None

Potential Workaround

None

Checklist

hide

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Folijet

Fix versions

Release

Poppy (R2 2023) Service Patch #5

CSP Approved

Yes

RCA Group

Implementation coding issue

Affected releases

Poppy (R2 2023)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created May 3, 2024 at 8:37 PM
Updated May 14, 2024 at 5:16 PM
Resolved May 7, 2024 at 12:29 PM

Activity

Show:

Maksym IshchenkoMay 10, 2024 at 8:50 AM

TestRail: Cases
TestRail: Runs