Guilds & credit sharing
How completed work is credited to everyone involved, and how guilds tune that for your organisation.
When an issue is completed, Aztra doesn't just credit the assignee. Credit is shared across every role involved in the work — and guilds let you tune how much each role's contribution counts for different job functions.
Who earns credit on a completed issue
- The assignee — the person responsible for doing the work earns the full share.
- The reviewer — whoever moves the issue through review earns review credit.
- The accountable lead — the sprint lead (or the project lead, if the issue isn't in a sprint) earns a share for owning the outcome.
- Consulted teammates — people marked as consulted on the issue earn a smaller share.
- Watchers — people kept informed earn a small share too.
Each person is credited once, at their highest role — and if the issue is reopened, the credit is reversed.
This is why marking who was consulted on an issue matters: advice, reviews, and unblocking are real contributions, and the leaderboard reflects them.
Guilds
A guild is a job function — Engineering, Design, QA, Product, and so on. Assign each workspace member to a guild, and the credit shares above can be weighted per guild, so the system reflects how different functions actually contribute in your organisation.
Create your guilds
In workspace settings, open the Guilds tab and create a guild per job function.
Assign members
Set each member's guild from the Members tab.
Start from a template
Apply one of the built-in organisation templates — presets shaped for different kinds of teams — then adjust individual weights to taste.
You don't have to configure any of this — sensible defaults apply out of the box. Reach for guild weights once you notice the leaderboard under- or over-valuing a function's contribution.
Related
- Leaderboard & points — where the credit shows up.
- Sprints — the sprint lead is the accountable role.