Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rewrite dynamic fields of types Agent, CustomerCompany and CustomerUser to reference-based fields #2637

Closed
stefanhaerter opened this issue Nov 2, 2023 · 2 comments
Labels
enhancement New feature or request
Milestone

Comments

@stefanhaerter
Copy link
Contributor

Conceptually and functionally, it makes more sense for the dynamic fields introduced in #2360 to be based on the reference field.

@stefanhaerter stefanhaerter added the enhancement New feature or request label Nov 2, 2023
@stefanhaerter stefanhaerter added this to the OTOBO 11.0 milestone Nov 2, 2023
@stefanhaerter
Copy link
Contributor Author

Important: It has to be ensured that the sub SearchFieldRender is adapted accordingly, mainly for the CustomerUser dynamic field.

stefanhaerter added a commit that referenced this issue Nov 23, 2023
stefanhaerter added a commit that referenced this issue Nov 23, 2023
svenoe pushed a commit that referenced this issue Nov 24, 2023
stefanhaerter added a commit that referenced this issue Nov 24, 2023
@stefanhaerter
Copy link
Contributor Author

Closed with merging #2734

stefanhaerter added a commit that referenced this issue Dec 12, 2023
…elds.

Introduced 'ConstantValue' for field type settings.
Both to restrict CustomerUser input type to autocomplete while maintaining field type settings structure.
stefanhaerter added a commit that referenced this issue Dec 12, 2023
CustomerUser driver manipulates the field type settings array now.
stefanhaerter added a commit that referenced this issue Dec 12, 2023
…etFieldTypeSettings in customer user driver instead.
stefanhaerter added a commit that referenced this issue Dec 12, 2023
svenoe pushed a commit that referenced this issue Dec 13, 2023
…elds.

Introduced 'ConstantValue' for field type settings.
Both to restrict CustomerUser input type to autocomplete while maintaining field type settings structure.
svenoe pushed a commit that referenced this issue Dec 13, 2023
CustomerUser driver manipulates the field type settings array now.
svenoe pushed a commit that referenced this issue Dec 13, 2023
…etFieldTypeSettings in customer user driver instead.
svenoe pushed a commit that referenced this issue Dec 13, 2023
stefanhaerter added a commit that referenced this issue Dec 29, 2023
svenoe pushed a commit that referenced this issue Jan 8, 2024
stefanhaerter added a commit that referenced this issue Jan 18, 2024
svenoe pushed a commit that referenced this issue Jan 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant