Whose name goes on a change

You moved the card, but the history says Laya Board. Or a colleague’s name. Or nobody you recognise. It looks like Laya got it wrong, or worse, like someone else has been editing your work — and neither is what happened.

A change can be written down in two places: in Laya, and in the tool the board is connected to. Each place will only put your name on something if it can prove the change came from you. Where it cannot, it records who it actually saw rather than guessing. This page shows exactly which name lands where, and what to do about it.

Find your situation

Answer two questions and you will get the one answer that applies to you. Every combination is also written out in full in the summary table further down, so you never have to use the picker.

Why it sometimes is not your name

Laya never assumes an identity on your behalf. Putting your name on a change is a claim about who did something, and a wrong claim is worse than a vague one — it misleads everyone reading the history afterwards, and it is the kind of mistake nobody notices until it matters.

So each side asks for its own proof:

• Laya credits you once you are signed in to Laya, or once the account you use elsewhere is genuinely tied to a Laya account.
• Jira credits you only when you have personally allowed Laya to act as you in Jira. Nobody else can grant that for you — not your admin, not the person who connected the workspace.

The two sides then fall back differently, and the difference is the whole point:

• Jira falls back to whoever it genuinely did see — the connection your workspace set up. That is why a change you made can appear in a Jira issue history as Laya Board (the app), or as the colleague who owns the connection. Jira can only attest to the access that made the write.
• Laya never does that. Inside Laya, a change is credited to your Jira name (tagged (Jira)) if Laya has mirrored you from this workspace’s Jira data, and to Unidentified Jira user if it has not. Crediting the person who set the connection up would put one named colleague’s name on everything an entire Jira site did, which is not a gap in the history so much as a wrong answer in it.

Laya will never match you by email address

The obvious shortcut would be to look at your work email in Jira, find a Laya account with the same address, and treat you as that person. Laya deliberately does not do this, anywhere.

An email address is not proof of identity: anyone can sign up somewhere using a colleague’s work address. If Laya paired accounts that way, creating a Laya account with your address would be enough to inherit your name on your team’s history. The only thing Laya accepts is a link you made yourself, by signing in to your Jira account and approving it — proof that both accounts really are you.

Connect your own Jira account

For most people this is the whole fix, and it takes about twenty seconds. Laya offers it to you at the moment it matters rather than hiding it in settings.

1. Open a board that syncs with JiraAny Laya board carrying Jira items will do.
2. Look at the banner across the top of the boardIt reads Your Jira edits aren’t attributed to you, and explains who your changes currently sync to Jira as — Laya Board (the app) or the workspace owner, whichever applies to your workspace.
3. Choose Connect JiraYou are taken to Atlassian to approve access — the same sign-in you already use for Jira. No password is typed into Laya, and you can revoke it later.
4. Carry onYou come straight back to the board. Every edit from then on is recorded in Jira as you.

Earlier changes are not rewritten. Jira histories are permanent records, and Laya cannot go back and re-sign something Jira has already stored. Connecting fixes everything from that point forward.

If you are already connected

Where a workspace connects Jira through the installed Laya Board app, members who have linked their own Jira access get a choice instead of a nudge: a banner reading Changes you make here sync to Jira as you, with a You / Laya Board switch. Pick whichever suits your team — some prefer a single, obvious app author on automated-looking changes. The setting is yours alone and you can change it at any time.

When changes are credited to the app on purpose

On a Jira-connected board, if you have not connected your own Jira, your edits reach Jira as Laya Board (the app). This is deliberate, and it is not a gap waiting to be closed.

• Your edit still works. It reaches Jira, and everyone sees the change.
• Jira’s history stays truthful: it names the connection that actually made the write, which is the only thing Jira can honestly attest to.
• Nothing is silently done in your name using access you never granted.
• The Laya side of the same change is still credited to you, so the work is never anonymous within Laya.

If you would rather your name appeared in Jira too, that is entirely in your hands — connect your own Jira.

Every situation at a glance

FAQs