# Segment Date Filters Bug

**URL:** <https://community.forestadmin.com/t/segment-date-filters-bug/5248>\
**Category:** Help me!\
**Created:** [September 13, 2022, 2:02pm UTC](https://community.forestadmin.com/t/segment-date-filters-bug/5248 "2022-09-13T14:02:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sarah\_Wessel](https://avatars.discourse-cdn.com/v4/letter/s/85e7bf/32.png) [@Sarah\_Wessel](https://community.forestadmin.com/u/Sarah_Wessel)\
**Post date:** [September 13, 2022, 2:02pm UTC](https://community.forestadmin.com/t/segment-date-filters-bug/5248/1 "2022-09-13T14:02:38Z")

</div>

## Feature(s) impacted

Segment filtering by date

## Observed behavior

When I create a date filter at the top of a table view, the filter works without issue. For example in the screenshot below, I am filtering by the column “proposed release date” and getting one result which matches that filter.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/a/aa485eed0400ba86f9e3044b0d9e596ce0faf0bf.png)

However, when I use that same filter to define a segment, I get no results.

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/f/ffef2f387807a545da45beca0487147f8119e843.png)

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/forest/original/2X/4/4ec42b6a162fa20af4f3dbf4f77f5f783629e697.png)

This problem seems to be specific to filtering on date fields. Filtering on other datatypes is working for me in segments.

## Expected behavior

I would expect the segment filtering to return the same results as non-segment filtering (the filter at the top of the table view). In this example, I would expect the segment to show the one matching row.

## Failure Logs

I am not getting any errors, just seeing unexpected behavior.

## Context

- Project name: GumboUI
- Team name: DepMap
- Environment name: I am seeing the same behavior in all of our environments (production, staging, and development)
- Agent type & version: django-forestadmin (v1.3.2)

---

<div class="post-metadata">

**Author:** ![anon39940173](https://avatars.discourse-cdn.com/v4/letter/a/8c91f0/32.png) [@anon39940173](https://community.forestadmin.com/u/anon39940173)\
**Post date:** [September 13, 2022, 2:06pm UTC](https://community.forestadmin.com/t/segment-date-filters-bug/5248/2 "2022-09-13T14:06:06Z")

</div>

Hi Sarah

A member of the team tech is trying to replicate the issue.

We’ll come back to you shortly (edit: tomorrow morning)

---

<div class="post-metadata">

**Author:** ![anon6357957](https://avatars.discourse-cdn.com/v4/letter/a/a698b9/32.png) [@anon6357957](https://community.forestadmin.com/u/anon6357957)\
**Post date:** [September 15, 2022, 8:15am UTC](https://community.forestadmin.com/t/segment-date-filters-bug/5248/4 "2022-09-15T08:15:31Z")

</div>

Hi @Sarah_Wessel,

I’m investigating your issue.

---

<div class="post-metadata">

**Author:** ![anon39940173](https://avatars.discourse-cdn.com/v4/letter/a/8c91f0/32.png) [@anon39940173](https://community.forestadmin.com/u/anon39940173)\
**Post date:** [September 15, 2022, 12:47pm UTC](https://community.forestadmin.com/t/segment-date-filters-bug/5248/5 "2022-09-15T12:47:20Z")

</div>

Hi @Sarah_Wessel

My coworkers told me that a patch was merged in the agent to solve that issue.  
Updating to 1.4.2 should get things working again