-
Notifications
You must be signed in to change notification settings - Fork 633
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
[Bug] CustomFields does not appear sorted in the case template #1383
Comments
Hello, is this issue true in RC3? |
Please reopen if this is still valid |
Reopening the issue as I can confirm it exists |
@To-om the orders of custom fields in case template are not taken into account when creating a case from a template |
The sequence of custom fields is still not preserved in alert and case creation for TH4. I set the order in the case template and checked the (equivalent) order being in the CustomFieldhelper.fields dictionary when using thehive4py for uploading a new alert (which should be imported as a case via the case template.) The dictionary shows: {'fieldname' : {'order': 0, 'string': 'ABCD'}, 'fieldname2': {'order': 1, 'string': 'EFGH'} .... }. When i create an empty case via the webinterface, the fields have the right order. But when using real data for creating an alert, the ordering is ignored. |
Request Type
Bug
Work Environment
Problem Description
Custom fields added to a template does not appear in that order when a case is created.
When the template is exported, the order fields is correct but that order is not followed when the case is shown in TheHive GUI.
Steps to Reproduce
The text was updated successfully, but these errors were encountered: