Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
-
ACQ Sprint 89, ACQ Sprint 90
-
1
-
Thunderjet
Description
Purpose: For acquisition units to be restricting actions they need to be applied to records
Acceptance criteria:
1)
Given acquisitions units have been created
When creating/editing organizations
Then the user can assign one or more acquisition units that they belong to, to the organization record.
TestRail: Results
Attachments
Issue Links
- blocks
-
UIORGS-182 UIORGS (ui-organizations) release
-
- Closed
-
- clones
-
UIORGS-78 Ability to add acquisition unit(s) to organization account(s)
-
- Closed
-
- has to be done after
-
MODORG-1 Project setup: mod-organizations
-
- Closed
-
-
MODORG-3 Restrict search/view of Organization records based upon acquisitions unit
-
- Closed
-
-
MODORG-4 Restrict updates of Organization records based upon acquisitions unit
-
- Closed
-
-
MODORG-5 Create business layer proxy API for organization operations
-
- Closed
-
-
MODORGSTOR-67 Add an "acqUnitIds" field to the organization schema
-
- Closed
-
- is blocked by
-
MODORG-11 Check restrictions for non-acq-unit members
-
- Closed
-
-
MODORGSTOR-48 Split organization account into separate table/API
-
- Closed
-
- relates to
-
MODORG-10 Migration script for organizations permissions
-
- Open
-
-
UXPROD-2055 Ability to use Acquisition units with Organization records
-
- Closed
-