Support
Velocity Chart for Jira
Get help
Have a question, found a bug, or want to request a feature? We're happy to help. Email us and we typically respond within 1–2 business days, or open a public issue on GitHub. Check the existing issues first: your question may already have an answer.
Email: support@janekbehrens.de
Bug reports & feature requests: github.com/janekbehrens/velocity-chart-for-jira-issues
Documentation: Velocity Chart for Jira documentation
Response time: 1–2 business days (Monday to Friday)
Before you reach out
Most questions are answered in the documentation. Common ones:
- "No closed sprints on this board yet" — velocity needs a Scrum board with at least one completed sprint. Kanban boards have no sprints.
- Numbers look empty — your issues are probably estimated in another field than the board's. In the gadget's Edit form, set Estimation to the field your team actually uses (Custom numeric field, for example Story point estimate) or to Issue count. Estimation is a Pro setting.
- A board is missing from the picker — only Scrum boards (company- and team-managed) in projects you can browse appear; classic Kanban boards are excluded because they have no sprints.
- Team-managed boards — fully supported; they appear in the picker tagged "team-managed".
- A colleague sees different numbers — everyone sees only the issues they can open in Jira (project permissions and issue security), as in Jira's own velocity chart; the line “N issues hidden” under the chart says how many are left out for you. See who sees which numbers.
What to include in a bug report
- Whether the board is company-managed or team-managed
- Your estimation mode (Story Points / issue count / custom field)
- What you expected vs. what you saw (a screenshot helps a lot)
Legal: Privacy Policy · Terms of Service · Security Policy