Skip to content

IA-4798: planning multiple target orgunit types#2830

Merged
beygorghor merged 9 commits intodevelopfrom
feat/IA-4798-planning-multiple-target-orgunit-types
Mar 20, 2026
Merged

IA-4798: planning multiple target orgunit types#2830
beygorghor merged 9 commits intodevelopfrom
feat/IA-4798-planning-multiple-target-orgunit-types

Conversation

@beygorghor
Copy link
Copy Markdown
Collaborator

What problem is this PR solving?

In this specific 2025 planning for instance, there were assignations made to all of these 5 levels Province, ZS, AS, HGR, CS. And the 2026 planning is expected to include at least 6 different OUT simultaneously.

Related JIRA tickets

IA-4798

Changes

  • adapt model, make migration, update the tests
  • change all frontend references to target_org_unit_type in the frontend (planning form, assignment page)

How to test

Create or edit a planning, make sure you can select multiple assignments levels.
Make sure everything is still working like before

Print screen / video

Screenshot 2026-03-18 at 15 11 41 Screenshot 2026-03-18 at 15 11 37

@quang-le quang-le added the release Should be released in production at next deploy label Mar 19, 2026
project,
description,
publishingStatus,
publishingStatus: publishingStatus ?? 'draft',
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

publishingStatus is never null-ish, it's already set to draft by default line 107

@beygorghor beygorghor merged commit 43e5ad1 into develop Mar 20, 2026
7 checks passed
@beygorghor beygorghor deleted the feat/IA-4798-planning-multiple-target-orgunit-types branch March 20, 2026 14:38
@beygorghor beygorghor added the user tested Has already been tested on staging label Mar 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

release Should be released in production at next deploy Released user tested Has already been tested on staging

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants