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

Regression on default values when creating entities in the context of a container #3921

Closed
SamuelHassine opened this issue Aug 3, 2023 · 1 comment · Fixed by #3932
Closed
Assignees
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)

Comments

@SamuelHassine
Copy link
Member

Description

Before:

  • New relationships / entities created in the context of a container inherit confidence level / marking definition from the container

After default value:

  • No inheritance
@SamuelHassine SamuelHassine added the bug use for describing something not working as expected label Aug 3, 2023
@SamuelHassine SamuelHassine added this to the Release 5.10.0 milestone Aug 3, 2023
@RomuDeuxfois RomuDeuxfois self-assigned this Aug 4, 2023
@SamuelHassine
Copy link
Member Author

SamuelHassine commented Aug 4, 2023

What we would like is that in the context of a container, default values are ignored (and inherited from the container for):

  • confidence level
  • marking definition
  • created by
  • when creating relationships, start_time / stop_time inherited from the container "created" date

We are talking about pre-filled the form, not on the backend side. The analyst can still change those values at creation.

@RomuDeuxfois RomuDeuxfois linked a pull request Aug 4, 2023 that will close this issue
5 tasks
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label Aug 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug use for describing something not working as expected solved use to identify issue that has been solved (must be linked to the solving PR)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants