I've run into a gap in Double's audit trail that's affecting our practice's oversight, and I wanted to flag it as both a bug report and a feature request.

The issue

When a transaction question is marked resolved/closed, there is no way to see which user closed it. This information doesn't appear on the question itself in the UI, and it doesn't appear in the activity log either, even though question_resolved is a defined activity log action.

Concrete example (Helen's Hands, LLC – client id 375065)

On Tuesday May 26, 2026 between 13:21:48 and 13:21:53 UTC (a 5-second window), 7 of my open transaction questions were bulk-closed without any client answer. The questions were:

20586466 (Purchase-4924)

20586447 (Purchase-5609)

20586446 (Purchase-5608)

20586441 (Purchase-5615)

20586410 (Purchase-4929)

20586409 (Purchase-4471)

20586395 (Purchase-5577)

All 7 were created by me on May 20, 2026. I did not close them, and the client never responded. I have no way to determine who in my practice (or anywhere) marked them resolved.

I queried the activity log for question_resolved and question_updated events on this client within that timestamp window and no events were returned, so it appears these resolutions are not being logged at all.

What I'd like

Bug fix: Ensure question_resolved activity is reliably written to the activity log with the resolving user's identity, every time a question is closed (manual, bulk, or via any other path).

Feature request: Surface the "closed by" user (and timestamp) directly on the question record in the UI and via the API, so practice admins/managers can see resolution attribution without digging through logs.

Same gap exists for transactions marked resolved inside the Uncategorized Transactions closing task — there's no per-transaction resolver attribution available anywhere I can find. Would love that captured as well.

This is important for us because resolving a question without answering it can hide unresolved items from a client's view and cause real coding mistakes downstream. Without an audit trail, we can't enforce process or coach team members appropriately.