MISP / MISP/misp-objects

Error: Value not in the right type/format. Please double check the value or select type "other".

Open
#319 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
110
Forks
139
Avg merge
12h 28m
Merged PRs (30d)
3

Description

When creating custom Template through "Event Actions > Add Template", user is not enforced to define Category and Type of an Attribute block, which in turn throws errors in an attempt to populate event.

This succeeds:
image

image

But when using the template, obviously it turns red:
image

Hence suggestion is to enforce user to define Attribute Category and Type when creating Template.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the Event Actions > Add Template flow and trace how custom Templates represent Attribute blocks. Check where Category and Type are validated before a template is saved, then verify that omitting either field is rejected and that valid templates still populate events without the reported type/format error.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
content
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.