Support

Support is async and email-first — and the product is built so you rarely need it. Start with the documentation; the four questions people actually ask are answered there.

Help us help you

Include what you can of the following — it usually turns a back-and-forth into a single reply:

• Your Jira site URL and the app name (e.g. True Time in Status).
• What you expected vs. what you saw — a screenshot is gold.
• The JQL of the report and the calendar selected (both shown in the report's meta bar).
• One example issue key where a number looks wrong. The per-day breakdown (click the cell) and the issue's History tab are how we'll both verify it.

Before you write in: the usual suspects

• A number looks an hour off → timezone. The built-in business-hours calendar uses your browser's timezone; create a custom calendar pinned to your team's zone.
• 0.0h in a status the issue definitely visited → it visited outside working hours (nights, weekends, holidays). Switch to the 24/7 calendar to compare.
• The report disagrees with my board → board columns are not statuses; one column can hold several statuses. The report measures the status field from the issue History.
• Two people get different issue counts → reports run with each viewer's own Jira permissions. That's by design.

Security

Suspected security issue? Email privacy@pipedcreations.com with "SECURITY" in the subject. Please don't post details publicly first.