Support

Trace Gap for Jira is built and supported by Bobook Limited, Dublin, Ireland.

Contact us

You are writing to the people who wrote the app. There is no ticket-deflection bot and no first-line script.

Response times

	Target
First reply	1 business day
A defect that blocks the report	Worked on the day it is reproduced
Feature requests	Answered honestly — including "no", with the reason

Business days are Monday to Friday, 09:00–18:00 Irish time (UTC / UTC+1).

What to include

The more of this you send, the faster the answer:

Your Jira site URL (for example yourcompany.atlassian.net)
The project key you ran the report on
Which issue types you selected as requirement and as verification
Which link types you selected, if any
What you expected the number to be, and what it showed instead
One example issue key that is classified wrongly

That last line is the most useful thing in the list. A single issue key that the report gets wrong is usually enough to find the cause.

Reporting a security issue

Please email support@bobook.club with "SECURITY" in the subject. Do not open a public report. We will acknowledge within one business day and keep you updated until it is resolved.

Before you write

Two things account for most surprises:

"Everything shows as a gap." Stock Jira Cloud has no is verified by link type — only Blocks, Cloners, Duplicate, Problem/Incident and Relates. If you selected a link type your project does not actually use, nothing will match. Clear the link-type field to accept any link and re-run.

"The number is lower than I expected." A requirement counts as covered only when the linked issue is one of the verification types you chose. A requirement linked to another requirement, or to a bug, is still a gap. That is deliberate.