Jira lists these components: Viewing content, Search, Automation for Jira.

When did the incident start and end?

It started at 2026-11-02 00:10 UTC and ended at 2026-11-02 00:38 UTC. It lasted 28 min.

How do I get alerts for Jira?

Subscribe to the Jira live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of Jira. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

JiraIncident · 2026-11-02 00:10 UTC

Fields missing across Jira Work Items for some users

Q: What happened?

Jira reported "Fields missing across Jira Work Items for some users" on its status page at 2026-11-02 00:10 UTC. Jira fields did not work in Work Items for some users. Viewing content, Search, and Automation for Jira were affected. Jira reports that the incident is resolved and lasted 28 minutes.

ResolvedOfficial update

Jira fields did not work in Work Items for some users. Viewing content, Search, and Automation for Jira were affected. Jira reports that the incident is resolved and lasted 28 minutes.

State

Resolved

Started

1 h ago

2026-11-02 00:10 UTC

Lasted

28 min

until 2026-11-02 00:38 UTC

Worst impact

Partial outage

Timeline

5 updates

00:1000:1700:2400:3100:38

Partial outageUpdate postedTimes in UTC

Investigating

19 min 68%

Monitoring

9 min 32%

Updates

Times in UTC

As posted by Jira

Monitoring2026-11-02 00:39 UTC

Our team has now identified a potential configuration change that appears to have caused this issue and has now reverted this change. We are now starting to see recovery across impacted operations for this issue and will be monitoring to check for a full recovery.

Resolved2026-11-02 00:38 UTC

We have now confirmed that all field related operations across the Jira, Jira Software Management, Jira Work Management and Jira Product Discovery should now be fully operational. We apologize for any inconvenience this may have caused.

Investigating2026-11-02 00:36 UTC

We are aware of an issue that is currently impacting fields across Work Items in Jira family products, including impacts to searching and automations on these fields. We are investigating with urgency and will update within one hour or sooner if we have further information to share.

Monitoring2026-11-02 00:27 UTC

Investigating2026-11-02 00:12 UTC

Affected components

Viewing contentSearchAutomation for Jira

Follow Jira

Your coding agent knows when Jira is down, and tells you when a failure is theirs, not yours. You can also get Jira incidents in a feed reader or in Slack.

Prompt

Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "jira" and tell me if Jira has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS

https://outages.cc/feed.xml?providers=jira

Slack

/feed subscribe https://outages.cc/feed.xml?providers=jira

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane