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.

Sign up for GitHub

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

Jump to bottom

[Bug] Prevent custom field creation if it already exists #2367

Closed
To-om opened this issue Apr 5, 2022 · 1 comment
Closed

[Bug] Prevent custom field creation if it already exists #2367

To-om opened this issue Apr 5, 2022 · 1 comment
Assignees
@To-om
Labels
bug TheHive4 TheHive4 related issues
Milestone
4.1.19

Comments

@To-om
Copy link
Contributor

To-om commented Apr 5, 2022

Request Type

Bug

Problem Description

It is possible to create several custom fields with the same name.
CustomField name should be unique, TheHive should prevent creation if it already exists.
@To-om To-om added bug TheHive4 TheHive4 related issues labels Apr 5, 2022
@To-om To-om added this to the 4.1.19 milestone Apr 5, 2022
@To-om To-om self-assigned this Apr 5, 2022
To-om added a commit that referenced this issue Apr 5, 2022
@To-om
#2367 Prevent custom field creation if it already exists
18cffae
@To-om To-om closed this as completed Apr 5, 2022
To-om added a commit that referenced this issue Apr 5, 2022
@To-om
#2367 Prevent custom field creation if it already exists
bd01858
@martinr103
Copy link

martinr103 commented Jun 3, 2022 •
edited
Loading

How exactly does it work for the 'Case merge' operation ?
When the two merged cases contain a custom field with the same name but different values -> what will happen in the resulting (merged) case ?
Still 2 custom fields with same name but 2 different values ?
1 custom field with 2 values ("multivalue") ?
Or will the merge operation fail ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@To-om To-om

Labels
bug TheHive4 TheHive4 related issues
Projects
None yet
Milestone
4.1.19
Development

No branches or pull requests
2 participants
@To-om @martinr103