Tally
Support
Something wrong? Tell me.
Tally is made by one person. Every report is read, and a bug with enough detail to reproduce is worth more than a five-star review.
Report it on GitHub
Best for bugs. The form asks for the few things needed to reproduce it, and you can follow what happens next.
A public repository for issues only — no code. You will need a GitHub account.
Or send an email
For anything else, or if you would rather not use GitHub. Same person reads both.
Please do not send screenshots containing customer names or issue summaries.
What helps most
- Your Tally version and browser. The version is in Settings, under About Tally, and Copy diagnostics beside it puts both on the clipboard along with the settings that change how Tally behaves — never a site address, an issue key, a summary or a name, and you can read every line before you paste it.
- What you expected, and what happened instead. Two sentences is plenty. “The week total said 32h but the rows add to 36h” is a bug report; “the totals are wrong” is a starting point for twenty questions.
- Whether it happens every time. A bug that happens once is worth reporting anyway — just say so, because it changes where to look.
A few things worth knowing
Tally is Jira Cloud only. Server and Data Center are not supported, and that is not a bug that can be reported away — the APIs are different.
If a whole view is empty, check Settings first: Tally shows only what your own Jira permissions return, so a project you cannot browse is correctly absent. The FAQ inside the extension covers the common cases.
Reviews get answered, but they are a poor place to report a bug. The store does not notify you when I reply, and there is no way to ask you a follow-up question. Either door above is faster for both of us.