Skip to content

[#72939] Jira import: status that doesn't exist on OP doesn't get assigned to the work package. Empty Group/Project required custom fields error.#22453

Merged
ba1ash merged 1 commit intodevfrom
bug/72939-jira-import-status-that-doesn-t-exist-on-op-doesn-t-get-assigned-to-the-work-package
Mar 23, 2026
Merged

[#72939] Jira import: status that doesn't exist on OP doesn't get assigned to the work package. Empty Group/Project required custom fields error.#22453
ba1ash merged 1 commit intodevfrom
bug/72939-jira-import-status-that-doesn-t-exist-on-op-doesn-t-get-assigned-to-the-work-package

Conversation

@ba1ash
Copy link
Member

@ba1ash ba1ash commented Mar 23, 2026

Ticket

https://community.openproject.org/work_packages/72939

What is inside?

  • Modify workflows of JiraMember role to allow all status transition for every type used during migration.
  • Use EmptyContract for Group and Project creation to avoid errors about empty required fields.

@ba1ash ba1ash requested a review from as-op March 23, 2026 11:41
@ba1ash ba1ash self-assigned this Mar 23, 2026
@ba1ash ba1ash force-pushed the bug/72939-jira-import-status-that-doesn-t-exist-on-op-doesn-t-get-assigned-to-the-work-package branch from 52fedc8 to e0b982b Compare March 23, 2026 11:43
Copy link
Contributor

@as-op as-op left a comment

Choose a reason for hiding this comment

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

LGTM 👍

@ba1ash ba1ash merged commit 07ceb0f into dev Mar 23, 2026
17 checks passed
@ba1ash ba1ash deleted the bug/72939-jira-import-status-that-doesn-t-exist-on-op-doesn-t-get-assigned-to-the-work-package branch March 23, 2026 12:35
@github-actions github-actions bot locked and limited conversation to collaborators Mar 23, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants