Use cases
Check your Jira tickets
Four questions Gescon answers by querying the Jira projects you authorise.
Product
«Which sprint is this issue in?»
Gescon queries Jira and returns the sprint, the status, and the owner.
Support
«Is there already an open ticket about this same error?»
Searches the authorised projects and returns related tickets.
Management
«How many critical tickets are still open?»
A count by priority and project.
Engineering
«Who closed this issue and when?»
Returns the owner, the closing date, and the resolution comment.
What it brings
What it reads and what it doesn't touch
The connector only queries. Nothing in Jira gets modified or reassigned.

- Authorised projectsOne by one: you choose which ones are in and which aren't.
- Tickets with their full contextStatus, sprint, owner, and recent comments.
- Ticket attachmentsFiles enter the repository like any other document.
- Citations to the source ticketEvery answer links to the exact ticket and its project.
- No changes madeThe connector is read-only. It doesn't create, close, or reassign tickets.
Setup
From authorisation to the first status
- Authorise the Jira projectWith an API token or OAuth, depending on your instance.
- Choose the projectsMark the ones you want Gescon to query.
- Ask as usualEvery answer cites the ticket and its source project.
Requirements
- Account with access to the projects to query
- API token or authorised Atlassian app
- A test project to validate before opening the rest
Estimated connection time: 15 min
Same family
OneDrive