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

Prevent users from accidentally creating duplicate objects (e.g. threat actors). #470

Closed
graememeyer opened this issue Feb 8, 2020 · 0 comments
Assignees
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Milestone

Comments

@graememeyer
Copy link

Please replace every line in curly brackets { like this } with appropriate answers, and remove this line.

Problem to Solve

{ Prevent users from accidentally creating duplicate objects (e.g. threat actors). }

Current Workaround

{ Basically have to manually make sure the threat actor / object doesn't already exist. }

Proposed Solution

{ I would suggest a warning pop-up if you type something that already exists into the name field for creating threat actors, attack patterns etc.

There's probably some more advanced stuff you could do around merging/modifying existing entries if a user attempts this, but a basic warning (or just straight-up not allowing the behaviour) would probably be a great feature. }

Additional Information

{ Tested in the demo environment (2.1.4) with FF and Chrome on Win10 }

@SamuelHassine SamuelHassine self-assigned this Feb 10, 2020
@SamuelHassine SamuelHassine added the feature use for describing a new feature to develop label Feb 10, 2020
@SamuelHassine SamuelHassine added this to the Release 3.0.1 milestone Feb 10, 2020
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label May 27, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature use for describing a new feature to develop solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

No branches or pull requests

2 participants