RovoAI “Create Jira work items” canceled, but it deleted all same‑day items across project.

[Ajinkya Jadhav]

Possible Rovo AI bug: clicking “No” after accidental “Create Jira work items” deleted unrelated work items in the project — can deleted items be recovered?

Hi everyone,

We are trying to confirm whether this is a known issue with Rovo AI and whether anyone else has experienced something similar.

What happened

One of our team members was viewing a Confluence page and opened Ask Rovo from the top-right corner. Instead of choosing “Summarize page”, they accidentally selected “Create Jira work items.” Atlassian documentation does confirm that Rovo can create Jira work items from a Confluence page / Rovo flow.

Rovo then created work items and showed a confirmation dialog asking whether to continue. Since this was accidental, the user selected “No.”

The problem

After clicking “No”, Rovo did delete the work items it had just created — but it also appears to have deleted other work items across multiple teams within the same project for that day, which were not intended to be removed.

Our questions

1. Is it possible to recover the deleted work items?
   From Atlassian’s Jira Cloud documentation, it looks like deleted work items cannot be restored from Atlassian backups, and recovery is only possible if we already have our own backup/export or enough notification history to recreate them manually. 

2. Is this a known issue with Rovo AI?
   I found public Rovo issues related to creation limitations and unsupported fields, but I could not find one that matches this exact behavior of unrelated items being deleted after canceling a Rovo-generated create flow.

3. Has anyone else seen this happen?
   We’d like to know whether this is reproducible, isolated, or already under investigation.

4. Are there any recommended safety precautions before enabling or using this feature in shared Jira projects?
   Atlassian documentation notes that deletion requires the Delete work items permission, so we are also reviewing whether this permission should be restricted more tightly for users testing AI-assisted actions.

Additional context

• This happened in Jira Cloud / Confluence Cloud
• The action started from Ask Rovo on a Confluence page
• The user intended to summarize the page, not create work items
• The issue seems to have affected more than just the newly created work items

If anyone from Atlassian or the community has seen this before, or can point us to a known bug / support article / best recovery path, we would really appreciate it.

Thanks in advance.

[Tinker Fadoua]

Welcome to the Atlassian Community @Ajinkya Jadhav !

This doesn't seem right. Deleting a work item that was created by mistake shouldn't delete other work items.

For the other work items that were deleted during the process they can be recovered only if they were created on a different day (this needs to be checked with Atlassian)

I am curious to know what could have triggered this behavior.

Atlassian Team will have to check the logs. You will need to raise a support ticket.

Best,

Fadoua