Hi e7355adaf86c, thanks for the update. I am quite disappointed to learn that Trello bugs and feature requests are managed in such a non-transparent way and unlike most other Atlassian products. I believe that the visibility and transparency of Atlassian bugs and feature requests is one of the greatest Atlassian support features and to learn that Trello are not already manging it in this way is rather disappointing. We, as end users no longer have any visibility of the bug details, status, impact, priority. We can't watch it, to be notified of updates and cannot vote to show that we are impacted. Do you know if there are any plans to make Trello feature requests and bugs publicly accessible, like most other Atlassian products? Is there a feature request for making this happen, or is that in the internal issue tracker also?

Hi all, Cody here from Trello support, we appreciate the diligence and understand how this issue negatively affects Trello user administration in your Atlassian Organizations.

Trello uses an internal issue tracker rather than the public issue tracker at jira.atlassian.com. We don't have an explicit timeline on when a fix for this will be prioritized, but I can confirm it's in our backlog, and all reports in this public ticket have been copied over to our internal tracker so no one's voice is lost.

To be sure we keep expectations set appropriately and responsibility for this is transparent, we will close this public ticket since it's currently assigned to a team that wouldn't be responsible for the underlying fix. 

Thank you again for your understanding - we won't be providing further public updates, but we're happy to field questions through https://trello.com/contact, and we will continue to track the impact of this issue through tickets created there.

I recently deactivated 51 Trello users, based on them seeming to have no information in Last active, Product access and Recent devices. Soon after it became apparent that these users were still and actively are using Trello, so they've been reactivated. However Atlassian should look to fix this as a matter of priority as this kind of misinformation is disruptive to end user's access and is also potentially a security risk, if leaver's Last active date is not being captured when it should. I'd also like to highlight that this issue is not just limited to Last active date. But also applies to: Product access and Recent devices sections which are both incorrectly showing despite users having product access and being active recently using some devices. Please fix ASAP.