Skip to content

[JIM-261] Custom field values are silently dropped when a type's form configuration changes in the same request or job - #26207

Merged
as-op merged 2 commits into
devfrom
bug/jim-261-custom-field-values-are-silently-dropped-when-a-type-s-form-configuration-changes-in-the-same-request-or-job
Oct 26, 2026
Merged

as-op merged 2 commits into
devfrom
bug/jim-261-custom-field-values-are-silently-dropped-when-a-type-s-form-configuration-changes-in-the-same-request-or-job

Conversation

@as-op

@as-op as-op commented Oct 21, 2026

Copy link
Copy Markdown
Contributor

Ticket

https://community.openproject.org/wp/JIM-261

What are you trying to accomplish?

Fixing a bug with custom field caching

What approach did you choose and why?

Clearing the cache if a custom field is added to a type's form configuration

Merge checklist

  • Added/updated tests

@klappradla klappradla left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Wow, quite a find 🦅

The fix makes sense 👍

Comment thread spec/workers/import/jira_create_project_work_packages_job_custom_fields_spec.rb Outdated
…om_fields_spec.rb

Co-authored-by: Max Mulatz <max@bitcrowd.net>
@as-op
as-op merged commit d8e1c39 into dev Oct 26, 2026
13 checks passed
@as-op
as-op deleted the bug/jim-261-custom-field-values-are-silently-dropped-when-a-type-s-form-configuration-changes-in-the-same-request-or-job branch October 26, 2026 12:30
@github-actions github-actions Bot locked and limited conversation to collaborators Oct 26, 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