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

Keep the alert date when creating a case from it #320

Closed
srilumpa opened this issue Sep 26, 2017 · 2 comments
Closed

Keep the alert date when creating a case from it #320

srilumpa opened this issue Sep 26, 2017 · 2 comments
Assignees

Comments

@srilumpa
Copy link

Request Type

Feature Request

We are automatically creating alerts and cases through the API. When we create an alert we set up its date with the data coming from our monitoring tools. Unfortunately, that date seems to be lost when we create a case from those alerts (using the /api/alert/${alert_id}/createCase) since the date of the case is its creation date.

How can we keep the alert date in the case? That information is rather critical when processing a case.

I think it could be really useful to keep somewhere in the case the date of the alert linked to it. Even more, since cases could be linked to several alerts (through merged cases), a good addition would be to have access to min date and max date or, even better, a timeline created from the alerts date.

In the mean time, we will probably try to use a case custom field to store that information.

Best regards

@saadkadhi saadkadhi added this to the 3.0.0 milestone Sep 28, 2017
@saadkadhi
Copy link
Contributor

Thanks @srilumpa. It makes perfect sense to carry the alert date over to the case when it is created, for ex. in its description. We will try to implement this missing and rather important functionality in Cerana (3.0).

@nadouani
Copy link
Contributor

The alert's date could be in fact set as the case's startDate field

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants