# Is it possible to set kibana.alert.workflow as mandatory field

**URL:** <https://discuss.elastic.co/t/is-it-possible-to-set-kibana-alert-workflow-as-mandatory-field/372840>\
**Category:** Elastic Security\
**Created:** [January 6, 2025, 11:32am UTC](https://discuss.elastic.co/t/is-it-possible-to-set-kibana-alert-workflow-as-mandatory-field/372840 "2025-01-06T11:32:36Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![marcou](https://avatars.discourse-cdn.com/v4/letter/m/278dde/32.png) [@marcou](https://discuss.elastic.co/u/marcou)\
**Post date:** [January 6, 2025, 11:32am UTC](https://discuss.elastic.co/t/is-it-possible-to-set-kibana-alert-workflow-as-mandatory-field/372840/1 "2025-01-06T11:32:36Z")

</div>

Hello everyone,  
We are looking for a way in Elastic Security to define the kibana.alert.workflow\_tags field as a mandatory field.  
The goal is that you cannot simply close alerts, but first have to set the kibana.alert.workflow\_tags field and only then you can close the alert or, even better, set it directly when closing it. 🙂

Why this:  
We have to regularly report how many of our alerts were false positive.  
To do this, we set the value "false positive" for false positive alerts.

The following requirement applies: Alert is "false positive" then set the value of "kibana.alert.workflow\_tags" to "false positive", if not or uncertain then open a case and set "kibana.alert.workflow\_tags" to "case".

Unfortunately, the value in kibana.alert.workflow\_tags is often forgotten, which then means additional, not insignificant effort and additional explanations to management.

Best regards

---

<div class="post-metadata">

**Author:** ![Jatin\_Kathuria](https://avatars.discourse-cdn.com/v4/letter/j/d6d6ee/32.png) [@Jatin\_Kathuria](https://discuss.elastic.co/u/Jatin_Kathuria)\
**Post date:** [January 24, 2025, 1:00pm UTC](https://discuss.elastic.co/t/is-it-possible-to-set-kibana-alert-workflow-as-mandatory-field/372840/2 "2025-01-24T13:00:08Z")

</div>

Hey @marcou ,

As of today, there is no way to achieve this. Although, it is in our roadmap to ask an Analyst for the `reason` of closing an alert but I cannot give any timeline on that.

When we start doing that, we will try to take your feeback in purview.

Thanks

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 21, 2025, 1:00pm UTC](https://discuss.elastic.co/t/is-it-possible-to-set-kibana-alert-workflow-as-mandatory-field/372840/3 "2025-02-21T13:00:31Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.