A Jira ticket is a decision record that nobody labels as one. The requirement, the objection, the compromise and the reason a scope was cut are all in the comment thread — and JQL is very good at finding tickets by field and very poor at finding them by what was said. The Jira connector is part of askFinz Knowledge, which is still rolling out; here is what it will do, and what it will not.
Find a ticket by what was discussed, not by its fields
Ask "the ticket where we decided not to support offline mode" and get it, even if nobody wrote "offline mode" in the summary. Comments are searched by meaning, which is the part JQL cannot do.
Answer "has this come up before?" in one question
Recurring bugs and repeated requests are expensive precisely because the previous round is hard to find. Connected, the earlier ticket surfaces with its resolution attached.
Carry sprint context into a document
Writing a status update or a post-mortem means pulling context back out of the board. Ask in Research and the answer cites the issue keys, so the reader can open each one.
What is read, and what is never changed
What crosses, and what stays in Jira
Read
issue summaries, descriptions, comments and status from the projects you select.
Written back
nonenothing. No issues created, transitioned or commented on.
Stored
a searchable copy of that text, plus a link back to the issue.
Never read
projects you did not select, and issues restricted from the connected account.
What you will be granting
Read-only access to the projects you choose, honouring the same project and issue-level permissions your Jira site already enforces.
Setting it up
Planned — not available yetWhat connecting it will look like once the connector arrives.
- 01
Authorise Jira from Knowledge and select the site.
- 02
Choose the projects to include.
- 03
Decide how far back to read — the last year, or the full history.
- 04
Set the refresh interval.
Limits, honestly
- One-way and read-only. Jira stays the place work is tracked.
- Answers reflect the last refresh, not the transition made a minute ago.
- Attachments, boards and dashboards are out of scope for now.
- Jira Service Management queues are handled as ordinary projects, without SLA fields.