[Request]: Filter by PublishedAt field

[geethag-tw]

Summary

Hi, we recently migrated from Strapi 4 to Strapi 5 and noticed that the admin UI no longer supports the ability to filter based on the draft/published status. While configuring the list view only createdAt and updatedAt fields are visible but publishedAt is missing.

Why is it needed?

When we have hundreds of content-types and want to manage it on the UI, the status filter would be helpful

Suggested solution(s)

No response

Related issue(s)/PR(s)

No response

[github-actions]

🤖 I've analyzed your question and here's what I found:

Thanks a lot for taking the time to report this and for sharing the context of your v4 → v5 migration — managing large volumes of content from the admin UI is a very real need, and relying on status/published filters is totally understandable.

1. What changed in Strapi 5

With Strapi 5, Draft & Publish and the way “status” works have been reworked, and the focus for status-based filtering is now on the Content API layer (REST, GraphQL, and Document Service) rather than the admin list-view UI:

• A new status parameter replaces publicationState and is used across:

  • REST API: status=published or status=draft[REST status; publicationState removed]
  • GraphQL API: status: PUBLISHED or status: DRAFT[GraphQL status]
  • Document Service API: status: 'published' | 'draft'[DS status]

• publishedAt is always present in Strapi 5:

  • If Draft & Publish is enabled:
    • Draft: publishedAt is null
    • Published: publishedAt is the publication date[Draft & Publish; publishedAt behavior]
  • If Draft & Publish is disabled: publishedAt is always set to the latest creation/edition date[publishedAt behavior]

However, the documentation you shared about the Content Manager configuration only mentions configuring search, filters, sort, and visible columns in the list view — it does not document any built‑in “filter by status” or “show publishedAt as a filter” in the Strapi 5 admin UI, only generic filter enablement and per-field sort/display options.[Content Manager config]

Because of that, and since there is no doc entry describing a status/publishedAt filter in the v5 admin UI, it’s very likely that:

• The status filter you were used to in v4 is not currently exposed as an out‑of‑the‑box list‑view filter in v5, and
• The fact that publishedAt is not available as a configurable filter field in the list view is a product gap / feature request, not just a documentation oversight.

2. Current alternatives

While the admin UI does not expose a dedicated status filter, you can still work with draft vs published content via the APIs:

a. REST API: filter by status

// Draft versions only
GET /api/articles?status=draft

// Published versions only (default if status is omitted)
GET /api/articles?status=published

publishedAt will be null for drafts in the response, which can help your tooling or dashboards distinguish them.[REST status]

You can also combine status with other filters:

GET /api/articles?status=published&filters[title][$containsi]=news

[REST filters; REST status]

b. Document Service API (backend / custom tools)

// All published documents
await strapi
  .documents('api::article.article')
  .findMany({ status: 'published' });

// All drafts
await strapi
  .documents('api::article.article')
  .findMany({ status: 'draft' });

[DS findMany; DS status]

This is useful if you build a small internal dashboard or automation to help your editors manage large volumes of content by status.

c. GraphQL API

If you’re using GraphQL:

query {
  articles(status: PUBLISHED) {
    documentId
    title
    publishedAt
  }
}

[GraphQL status]

3. About the missing admin filter / publishedAt in list view

From the docs available:

• We do not have documented support in Strapi 5 for:
  • Adding a “status” filter directly in the Content Manager list view, or
  • Using publishedAt specifically as a built‑in filter field in that view.[Content Manager config]

So your observation after migrating from v4 is valid: this is either:

• A missing feature compared to v4 UX, or
• A product enhancement request to bring status / publishedAt filtering into the list view configuration options.

There’s nothing in the current migration/breaking changes docs that says this behavior is configurable in the admin, only that:

• publicationState has been removed and replaced by status at the API level, and
• publishedAt behavior has changed and is always present.[publicationState removed; publishedAt behavior]

4. Next steps / suggestion

Given your use case (hundreds of entries, editor-centric management in the UI), this is a very reasonable feature request.

• I’d recommend opening or upvoting a request on our public roadmap/feedback portal so it can be properly tracked:
  👉 https://feedback.strapi.io
  You can mention that:

  • In Strapi 4 you relied on admin UI status/published filtering,
  • In Strapi 5 you’d like:
    • publishedAt to be available as a field in the list-view configuration, and/or
    • a dedicated “Status” filter (Draft / Published / Modified).

• If this GitHub issue is filed in a docs repo but it turns out to be about core product behavior, it likely needs core-team attention as a product/UX improvement rather than documentation only. In that case it would be good to flag it for transfer to the main strapi/strapi repository for visibility by the product and engineering team, e.g. pinging @pwizla.

In the meantime, for teams that absolutely need status-based management at scale today, the most practical workaround is to:

1. Use the REST / GraphQL / Document Service APIs with status and publishedAt in a small internal tool or dashboard, and
2. Use the standard list view configuration (search, filters, sort, visible columns) in the admin UI for everything else.[REST status; DS status]

If you can share which content types and workflows are most impacted (e.g., specific editorial flows, release processes), that context can also help the team better assess and prioritize improvements around status filtering in the admin UI.

📚 Relevant documentation:

• publicationState is removed and replaced by status
• Content Manager - Configuration
• Content types always have feature columns
• Content types with Draft & Publish disabled always have the publishedAt value set to a date
• CRUD operations with the Entity Service API
• Document Service API - findMany()
• Document Service API: Usage with Draft & Publish
• Draft & Publish
• Draft & Publish - Usage
• Entity Service deprecated
• GraphQL API - Fetch draft or published versions
• REST API parameters
• REST API: status
• REST API: Filters
• Strapi v4 to Strapi 5 breaking changes - Content API

---

ℹ️ This response was generated automatically. If this doesn't fully answer your question or if you need further assistance, please mention @pwizla in a comment and a human maintainer will help you.

You can also try our interactive AI chat for more detailed assistance.

💡 For feature requests or product feedback, visit feedback.strapi.io.

[geethag-tw]

@pwizla Is there any workaround for us to get this working?

[pwizla]

Hi @geethag-tw and thanks for flagging me. I'm sorry you're running into this migration hiccup.
I'll pass this to the engineering team. If there's no current quick workaround, you will have to create a feature request (on feedback.strapi.io) as explained by the AI bot.

[geethag-tw]

Thank you @pwizla, appreciate the quick response. Introducing this feature will greatly help in managing the content-types through the admin panel. Looking forward to it.

[pwizla]

Hey @geethag-tw ! There actually already is a pull request in the product codebase to make the publishedAt field visible 😊
Hoping this will get merged soon!

You can test it locally if you want, maybe with some sample data exported with our Data Management feature, to confirm it will solve your issue once the Strapi feature is shipped to production. Would you need further help with that?

[geethag-tw]

That's awesome, thank you for the update. I will check it out and let you know if it solves our issue.