nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Why are my filters broken all of a sudden? Error: The value 'Open' does not exist for the field 'sta

unknown

I visited my dashboard this morning and everything was working fine (all filters etc) this afternoon I have an error on all of the filters using "open" for status. I thought Open was the default for when a task was opened. These filters worked fo the last year so I am confused why they stopped.

The value 'Open' does not exist for the field 'status'.

Accepted answers

Nich Hogue

Hi Jennifer

I would double check that Open still exists for the tickets. The first thing that comes to mind with how these filters would break is that someone modified your workflow. It's possible to re-name an issue status, or update your workflow and remove/replace that status. So that's why it's the first place I would check in the actual tickets.

All comments

Nich Hogue

Hi Jennifer

unknown

There is no longer an open status you are correct it now seems to be a software tight status but I didn’t change anything how could this be changed? Where would this be changed? I checked all of my workflows and they seem to be the same. I was not in the Jira admin at all

Nich Hogue

Most likely what happened is another admin went in to their workflow that also had Open as a status and changed it to software tight. Statuses are shared across all of a Jira instance. Unlike transitions if you re-name a status it renames it globally not just in one project.

If you have admin and can check the Audit Log if your cloud instance has Atlassian Access, https://confluence.atlassian.com/cloud/audit-logging-970612562.html . From there you can see who performed the change and help educate.

Alexander Stern _ Shern Consulting OÜ

Issues like this can be quite frustrating, especially when something “just changes” without an obvious reason.

In many cases, it turns out to be related to underlying configuration changes — statuses, workflows, or permissions — rather than the filter itself.

The tricky part is usually tracing back what changed and when, since that’s not always immediately visible.

Having a clearer way to review recent configuration changes can make these situations much easier to diagnose.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-core

jira-core-cloud