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

Observables dates (creation and modification) required seconds precision #462

Closed
Fred-certeu opened this issue Feb 4, 2020 · 0 comments
Closed
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

@Fred-certeu
Copy link

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

Problem to Solve

For openCTI entities the creation and modification date just indicate the date (not the time)
For most entities, this is acceptable.
But for observables (at least) a more precise timing info is needed : date + time (hh:mm:ss)
For example, when a connector will import large sets of observables everyday (typically every xx minutes), it becomes very useful to filter at the time level (not just the date).

Current Workaround

None

Proposed Solution

Implement time level information for observables : creation and modification time.

Additional Information

{ Any additional information, including logs or screenshots if you have any. }

@richard-julien richard-julien changed the title Date & Time Observables dates (creation and modification) required seconds precision Feb 5, 2020
@richard-julien richard-julien added the feature use for describing a new feature to develop label Feb 5, 2020
@SamuelHassine SamuelHassine added this to the Release 3.1.2 milestone Apr 23, 2020
@SamuelHassine SamuelHassine self-assigned this Apr 23, 2020
@SamuelHassine SamuelHassine added the solved use to identify issue that has been solved (must be linked to the solving PR) label May 25, 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

3 participants