What's the delay of the dashboard getting moved to the trash? This happened to our organization but the only users that were deactivated were deactivated days before the dashboards moved. That and I don't think those users were likely to own the number of dashboards that we lost.

Providing a summary of the current state on this ticket for clarity: * Currently when a user is removed from a Jira site, their dashboards, filters etc. will be moved to trash

• Admins have the ability to restore trashed dashboards for 60 days. You can read more about this behaviour here.
• This behaviour is not unique to Dashboards - Filters, Favourited entities, Subscriptions etc. all follow a consistent pattern.

At this stage, we are not looking to change this behaviour, and any change would require a widespread review of the treatment of all items. 

Hi 87c8957beabb I have created a feature request on your behalf, here: JRACLOUD-81094 - When a user is deleted from a site, their dashboards should not be moved to trash

I am now the owner of 97 dashboards rescued from the trash after their creator unexpectedly parted ways with my employer. 

Automatic dashboard deletion–intended or not–is a real problem.

I don't know what the ideal solution to that problem is, but "wait for users to notice their dashboards are gone, and then send your admins to dig through the trash like panicked vultures" isn't it.

I found a workaround. If you go to manage system dashboards, check "Show dashboards moved to trash" and restore them, they will come back under your name.

https://xxxxxxxxxx.atlassian.net/secure/admin/dashboards/ViewSharedDashboards.jspa

Hey Jira Product Team, this is a pretty big pain point. Please move this to a possible enhancement. While this may not be a bug, it's definitely not intuitive to the admins if this is happening in multiple teams/firms.

Can anybody tag Nara So on this since she's the assignee?

Hi @Nara So and @Thuan Nguyen - What if the user is automatically removed/deactivated (legitimately) by the AD connection? ...we have no way of reassigning the Dashboards at that point. The Dashboards are automatically moved to the Trash and our teams lose access to them. They have to be Restored and assigned a new Owner in order for the teams to access them again. It'd be nice if JIRA honored the View/Edit permissions regardless of whether or not the Owner is still an active user.

I'm having a hard time believing that this is actually "intended" behavior. I'm more inclined to believe that this is a Bug (or poor design) that was carried over from the Server version. I kindly ask that you (Atlassian) consider reopening this "Bug" or (at minimum) changing it to a "Suggestion". Thanks!

Thanks for raising the bug and investigating further nso@atlassian.com and f8dac69712b5.

This behaviour is actually intended, carried over from Server. We will take the necessary steps to ensure our Cloud documentation is updated to reflect this.

When JRACLOUD-17783 is resolved, users will be able to transfer edit ownership over to another user. Users can then do this before their account is deleted, which should mitigate any issues with lost dashboards.