Jira Status

Resolved: The vast majority of customers historical events have now all been processed successfully, with a small group of customers that have very high volume of automations still to process which are actively underway. We expect these remaining processes to be completed within approximately two hours, if not sooner.

Monitoring: Processing of the historical events is still occurring with our team monitoring progress closely. We will be providing a further update either when these tasks are fully completed or within 4 hours, whichever is earlier.

Monitoring: We have successfully completed the replay for most regions, with remainder expected to finish in next 3 hours.

Monitoring: We are replaying historical events for affected customers to rerun Automation rules that failed to execute between March 18, 10:00 AM UTC and 1:45 PM UTC. We are closely monitoring the results of this replay and will post an update in a few hours when this work is complete.

Monitoring: We have identified the cause of the issue and deployed changes that have restored automation processing for Jira and Jira Service Management. Automations are now triggering as expected. We will continue to monitor closely to confirm stability.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: Customers using Jira and Jira Service Management are currently experiencing an issue where automations do not trigger for actions such as work item creation, field updates, and comment additions, although manual triggers remain functional. We'll share updates here as more information is available.

Investigating: Some customers may experience automations not triggering for specific actions such as work item creation, updates, and comment additions. However, manually triggered automations are operating as expected.

Investigating: We are investigating reports of intermittent errors for SOME Jira Cloud customers for Automations triggering. We will provide more details once we identify the root cause.

Resolved: The vast majority of customers historical events have now all been processed successfully, with a small group of customers that have very high volume of automations still to process which are actively underway. We expect these remaining processes to be completed within approximately two hours, if not sooner.

Monitoring: Processing of the historical events is still occurring with our team monitoring progress closely. We will be providing a further update either when these tasks are fully completed or within 4 hours, whichever is earlier.

Monitoring: We have successfully completed the replay for most regions, with remainder expected to finish in next 3 hours.

Monitoring: We are replaying historical events for affected customers to rerun Automation rules that failed to execute between March 18, 10:00 AM UTC and 1:45 PM UTC. We are closely monitoring the results of this replay and will post an update in a few hours when this work is complete.

Monitoring: We have identified the cause of the issue and deployed changes that have restored automation processing for Jira and Jira Service Management. Automations are now triggering as expected. We will continue to monitor closely to confirm stability.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: Customers using Jira and Jira Service Management are currently experiencing an issue where automations do not trigger for actions such as work item creation, field updates, and comment additions, although manual triggers remain functional. We'll share updates here as more information is available.

Investigating: Some customers may experience automations not triggering for specific actions such as work item creation, updates, and comment additions. However, manually triggered automations are operating as expected.

Investigating: We are investigating reports of intermittent errors for SOME Jira Cloud customers for Automations triggering. We will provide more details once we identify the root cause.

Resolved: The vast majority of customers historical events have now all been processed successfully, with a small group of customers that have very high volume of automations still to process which are actively underway. We expect these remaining processes to be completed within approximately two hours, if not sooner.

Monitoring: Processing of the historical events is still occurring with our team monitoring progress closely. We will be providing a further update either when these tasks are fully completed or within 4 hours, whichever is earlier.

Monitoring: We have successfully completed the replay for most regions, with remainder expected to finish in next 3 hours.

Monitoring: We are replaying historical events for affected customers to rerun Automation rules that failed to execute between March 18, 10:00 AM UTC and 1:45 PM UTC. We are closely monitoring the results of this replay and will post an update in a few hours when this work is complete.

Monitoring: We have identified the cause of the issue and deployed changes that have restored automation processing for Jira and Jira Service Management. Automations are now triggering as expected. We will continue to monitor closely to confirm stability.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: Customers using Jira and Jira Service Management are currently experiencing an issue where automations do not trigger for actions such as work item creation, field updates, and comment additions, although manual triggers remain functional. We'll share updates here as more information is available.

Investigating: Some customers may experience automations not triggering for specific actions such as work item creation, updates, and comment additions. However, manually triggered automations are operating as expected.

Investigating: We are investigating reports of intermittent errors for SOME Jira Cloud customers for Automations triggering. We will provide more details once we identify the root cause.

Resolved: The vast majority of customers historical events have now all been processed successfully, with a small group of customers that have very high volume of automations still to process which are actively underway. We expect these remaining processes to be completed within approximately two hours, if not sooner.

Monitoring: Processing of the historical events is still occurring with our team monitoring progress closely. We will be providing a further update either when these tasks are fully completed or within 4 hours, whichever is earlier.

Monitoring: We have successfully completed the replay for most regions, with remainder expected to finish in next 3 hours.

Monitoring: We are replaying historical events for affected customers to rerun Automation rules that failed to execute between March 18, 10:00 AM UTC and 1:45 PM UTC. We are closely monitoring the results of this replay and will post an update in a few hours when this work is complete.

Monitoring: We have identified the cause of the issue and deployed changes that have restored automation processing for Jira and Jira Service Management. Automations are now triggering as expected. We will continue to monitor closely to confirm stability.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: Customers using Jira and Jira Service Management are currently experiencing an issue where automations do not trigger for actions such as work item creation, field updates, and comment additions, although manual triggers remain functional. We'll share updates here as more information is available.

Investigating: Some customers may experience automations not triggering for specific actions such as work item creation, updates, and comment additions. However, manually triggered automations are operating as expected.

Investigating: We are investigating reports of intermittent errors for SOME Jira Cloud customers for Automations triggering. We will provide more details once we identify the root cause.

Resolved: The vast majority of customers historical events have now all been processed successfully, with a small group of customers that have very high volume of automations still to process which are actively underway. We expect these remaining processes to be completed within approximately two hours, if not sooner.

Monitoring: Processing of the historical events is still occurring with our team monitoring progress closely. We will be providing a further update either when these tasks are fully completed or within 4 hours, whichever is earlier.

Monitoring: We have successfully completed the replay for most regions, with remainder expected to finish in next 3 hours.

Monitoring: We are replaying historical events for affected customers to rerun Automation rules that failed to execute between March 18, 10:00 AM UTC and 1:45 PM UTC. We are closely monitoring the results of this replay and will post an update in a few hours when this work is complete.

Monitoring: We have identified the cause of the issue and deployed changes that have restored automation processing for Jira and Jira Service Management. Automations are now triggering as expected. We will continue to monitor closely to confirm stability.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: Customers using Jira and Jira Service Management are currently experiencing an issue where automations do not trigger for actions such as work item creation, field updates, and comment additions, although manual triggers remain functional. We'll share updates here as more information is available.

Investigating: Some customers may experience automations not triggering for specific actions such as work item creation, updates, and comment additions. However, manually triggered automations are operating as expected.

Investigating: We are investigating reports of intermittent errors for SOME Jira Cloud customers for Automations triggering. We will provide more details once we identify the root cause.

Resolved: The vast majority of customers historical events have now all been processed successfully, with a small group of customers that have very high volume of automations still to process which are actively underway. We expect these remaining processes to be completed within approximately two hours, if not sooner.

Monitoring: Processing of the historical events is still occurring with our team monitoring progress closely. We will be providing a further update either when these tasks are fully completed or within 4 hours, whichever is earlier.

Monitoring: We have successfully completed the replay for most regions, with remainder expected to finish in next 3 hours.

Monitoring: We are replaying historical events for affected customers to rerun Automation rules that failed to execute between March 18, 10:00 AM UTC and 1:45 PM UTC. We are closely monitoring the results of this replay and will post an update in a few hours when this work is complete.

Monitoring: We have identified the cause of the issue and deployed changes that have restored automation processing for Jira and Jira Service Management. Automations are now triggering as expected. We will continue to monitor closely to confirm stability.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: Customers using Jira and Jira Service Management are currently experiencing an issue where automations do not trigger for actions such as work item creation, field updates, and comment additions, although manual triggers remain functional. We'll share updates here as more information is available.

Investigating: Some customers may experience automations not triggering for specific actions such as work item creation, updates, and comment additions. However, manually triggered automations are operating as expected.

Investigating: We are investigating reports of intermittent errors for SOME Jira Cloud customers for Automations triggering. We will provide more details once we identify the root cause.

Resolved: The vast majority of customers historical events have now all been processed successfully, with a small group of customers that have very high volume of automations still to process which are actively underway. We expect these remaining processes to be completed within approximately two hours, if not sooner.

Monitoring: Processing of the historical events is still occurring with our team monitoring progress closely. We will be providing a further update either when these tasks are fully completed or within 4 hours, whichever is earlier.

Monitoring: We have successfully completed the replay for most regions, with remainder expected to finish in next 3 hours.

Monitoring: We are replaying historical events for affected customers to rerun Automation rules that failed to execute between March 18, 10:00 AM UTC and 1:45 PM UTC. We are closely monitoring the results of this replay and will post an update in a few hours when this work is complete.

Monitoring: We have identified the cause of the issue and deployed changes that have restored automation processing for Jira and Jira Service Management. Automations are now triggering as expected. We will continue to monitor closely to confirm stability.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: Customers using Jira and Jira Service Management are currently experiencing an issue where automations do not trigger for actions such as work item creation, field updates, and comment additions, although manual triggers remain functional. We'll share updates here as more information is available.

Investigating: Some customers may experience automations not triggering for specific actions such as work item creation, updates, and comment additions. However, manually triggered automations are operating as expected.

Investigating: We are investigating reports of intermittent errors for SOME Jira Cloud customers for Automations triggering. We will provide more details once we identify the root cause.

Resolved: The vast majority of customers historical events have now all been processed successfully, with a small group of customers that have very high volume of automations still to process which are actively underway. We expect these remaining processes to be completed within approximately two hours, if not sooner.

Monitoring: Processing of the historical events is still occurring with our team monitoring progress closely. We will be providing a further update either when these tasks are fully completed or within 4 hours, whichever is earlier.

Monitoring: We have successfully completed the replay for most regions, with remainder expected to finish in next 3 hours.

Monitoring: We are replaying historical events for affected customers to rerun Automation rules that failed to execute between March 18, 10:00 AM UTC and 1:45 PM UTC. We are closely monitoring the results of this replay and will post an update in a few hours when this work is complete.

Monitoring: We have identified the cause of the issue and deployed changes that have restored automation processing for Jira and Jira Service Management. Automations are now triggering as expected. We will continue to monitor closely to confirm stability.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: Customers using Jira and Jira Service Management are currently experiencing an issue where automations do not trigger for actions such as work item creation, field updates, and comment additions, although manual triggers remain functional. We'll share updates here as more information is available.

Investigating: Some customers may experience automations not triggering for specific actions such as work item creation, updates, and comment additions. However, manually triggered automations are operating as expected.

Investigating: We are investigating reports of intermittent errors for SOME Jira Cloud customers for Automations triggering. We will provide more details once we identify the root cause.

Resolved: The vast majority of customers historical events have now all been processed successfully, with a small group of customers that have very high volume of automations still to process which are actively underway. We expect these remaining processes to be completed within approximately two hours, if not sooner.

Monitoring: Processing of the historical events is still occurring with our team monitoring progress closely. We will be providing a further update either when these tasks are fully completed or within 4 hours, whichever is earlier.

Monitoring: We have successfully completed the replay for most regions, with remainder expected to finish in next 3 hours.

Monitoring: We are replaying historical events for affected customers to rerun Automation rules that failed to execute between March 18, 10:00 AM UTC and 1:45 PM UTC. We are closely monitoring the results of this replay and will post an update in a few hours when this work is complete.

Monitoring: We have identified the cause of the issue and deployed changes that have restored automation processing for Jira and Jira Service Management. Automations are now triggering as expected. We will continue to monitor closely to confirm stability.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: Customers using Jira and Jira Service Management are currently experiencing an issue where automations do not trigger for actions such as work item creation, field updates, and comment additions, although manual triggers remain functional. We'll share updates here as more information is available.

Investigating: Some customers may experience automations not triggering for specific actions such as work item creation, updates, and comment additions. However, manually triggered automations are operating as expected.

Investigating: We are investigating reports of intermittent errors for SOME Jira Cloud customers for Automations triggering. We will provide more details once we identify the root cause.

Resolved: The vast majority of customers historical events have now all been processed successfully, with a small group of customers that have very high volume of automations still to process which are actively underway. We expect these remaining processes to be completed within approximately two hours, if not sooner.

Monitoring: Processing of the historical events is still occurring with our team monitoring progress closely. We will be providing a further update either when these tasks are fully completed or within 4 hours, whichever is earlier.

Monitoring: We have successfully completed the replay for most regions, with remainder expected to finish in next 3 hours.

Monitoring: We are replaying historical events for affected customers to rerun Automation rules that failed to execute between March 18, 10:00 AM UTC and 1:45 PM UTC. We are closely monitoring the results of this replay and will post an update in a few hours when this work is complete.

Monitoring: We have identified the cause of the issue and deployed changes that have restored automation processing for Jira and Jira Service Management. Automations are now triggering as expected. We will continue to monitor closely to confirm stability.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: Customers using Jira and Jira Service Management are currently experiencing an issue where automations do not trigger for actions such as work item creation, field updates, and comment additions, although manual triggers remain functional. We'll share updates here as more information is available.

Investigating: Some customers may experience automations not triggering for specific actions such as work item creation, updates, and comment additions. However, manually triggered automations are operating as expected.

Investigating: We are investigating reports of intermittent errors for SOME Jira Cloud customers for Automations triggering. We will provide more details once we identify the root cause.

Resolved: The vast majority of customers historical events have now all been processed successfully, with a small group of customers that have very high volume of automations still to process which are actively underway. We expect these remaining processes to be completed within approximately two hours, if not sooner.

Monitoring: Processing of the historical events is still occurring with our team monitoring progress closely. We will be providing a further update either when these tasks are fully completed or within 4 hours, whichever is earlier.

Monitoring: We have successfully completed the replay for most regions, with remainder expected to finish in next 3 hours.

Monitoring: We are replaying historical events for affected customers to rerun Automation rules that failed to execute between March 18, 10:00 AM UTC and 1:45 PM UTC. We are closely monitoring the results of this replay and will post an update in a few hours when this work is complete.

Monitoring: We have identified the cause of the issue and deployed changes that have restored automation processing for Jira and Jira Service Management. Automations are now triggering as expected. We will continue to monitor closely to confirm stability.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: We continue to investigate the issue, and the next communication will be issued in 60 minutes, or sooner if a significant milestone is achieved.

Investigating: Customers using Jira and Jira Service Management are currently experiencing an issue where automations do not trigger for actions such as work item creation, field updates, and comment additions, although manual triggers remain functional. We'll share updates here as more information is available.

Investigating: Some customers may experience automations not triggering for specific actions such as work item creation, updates, and comment additions. However, manually triggered automations are operating as expected.

Investigating: We are investigating reports of intermittent errors for SOME Jira Cloud customers for Automations triggering. We will provide more details once we identify the root cause.