Collaboration
Getting a ticket attributed to the right place
Correcting the submitter, organisation and tribe on a ticket, and why it matters for your reporting.
Last updated September 2, 2026
A ticket records who raised it and which organisation and tribe it came from. Tickets arriving by email often arrive with that wrong or missing — an unfamiliar address, a personal account, a forwarded message.
What can be corrected
| Field | Fix it when |
|---|---|
| Submitter | The ticket is attributed to the wrong person, or to an address rather than a known user. |
| Originating organisation | It arrived without one, or against the wrong one. |
| Originating tribe | You know which tribe it is really about. |
Changing the submitter can notify the new one, so they can follow the ticket they are now on.
Why it is worth the ten seconds
- Support load per tribe is only meaningful if tickets are attributed.
- A ticket with no organisation is invisible in every per-organisation view.
- The person who actually raised it should be the one told when it is resolved.
DO IT ON ARRIVAL
Attribution is easy while the ticket is fresh and nearly impossible three weeks later. Fix it as part of picking the ticket up.