Conversation
🤖 Augment PR SummarySummary: Resolves current viewer identity for Jira, Linear, and Trello integrations.
🤖 Was this summary useful? React with 👍 or 👎 |
![augmentcode[bot]](https://avatars.githubusercontent.com/in/1027498?s=60&v=4){kind=small}
getProviderCurrentAccount (the hook getCurrentAccount's cache relies on) was only implemented for the git hosts and Azure DevOps, so consumers had no way to know which issues in a Jira/Linear/Trello read belonged to the current user even though the underlying issue fetch worked fine. Jira resolves the account against its first visible resource (there's no account-wide "who am I" endpoint there); Linear and Trello's own account lookups already ignore the resource argument, so their per-resource and current-account paths now share one implementation. listIssueTrackerIssuesPage also fires (but doesn't await) getCurrentAccount once per read: PR and sweep reads already trigger it via getCurrentAccountId, but issue reads never did, so nothing populated the cache for any provider on that path.
The background getCurrentAccount trigger ran before forceRefreshIfRequested, so a forced sync could populate the account cache from the pre-refresh session and spuriously record a stale-token failure.
listIssueTrackerIssuesPage's mapper reads getCurrentAccount's cache synchronously right after the read call returns. A fire-and-forget call races that read, so the first page's assignedToMe/authoredByMe can stay unresolved with nothing to remap it later.
sergiolms
force-pushed
the
fix/issue-tracker-viewer-identity
branch
from
September 14, 2026 12:29
c077b8d to
6277f04
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Integration.getCurrentAccount()resolves the current user via the protectedgetProviderCurrentAccounthook, but that hook was only implemented for the git-hosting providers (GitHub, GitLab, Bitbucket, Azure DevOps). Jira, Linear and Trello had no way to answer "who is the current user", so a consumer reading issues from those trackers had no basis for viewer-relative flags (assigned-to-me, authored-by-me).This adds
getProviderCurrentAccountto all three:listIssueTrackerIssuesPagealso fires (without awaiting)integration.getCurrentAccount()once per read. PR and sweep reads already trigger it viagetCurrentAccountId, but issue reads never did, so nothing populated the cache for any provider on that path.Checklist
Fixes $XXX -orCloses #XXX -prefix to auto-close the issue that your PR addresses - N/A, no pre-existing issue; happy to file one if preferred