Routing client requests to Jira, GitHub, and Linear
Connect your team's development backlogs to easily route client portal change requests into active developer tickets.
5 min read
Authorize ticketing integrations
Connect your agency's development software. Open 'Integrations' under Manage in the sidebar and authorize connections for Jira Cloud, GitHub, Linear, Asana, ClickUp, GitLab, Azure DevOps, or Trello. The OAuth process registers secure API tokens to fetch active projects, boards, and users dynamically.
Export a request to your tracker
Open a change request's details and use 'Export to Task Tracker'. Pick the connected platform and its fields (project, repo, team, list, board, etc.) are fetched live and shown as dropdowns - not typed by hand - with the first option pre-selected and priority/due date carried over from the request where the provider supports it. Everything's still editable before you confirm. The created issue carries the client's description, linked back to this request.
The same picker works from report findings
The identical 'Create issue' flow is available on any failing or warning finding inside a site report, with the same live dropdowns - so a failed check can go straight to a developer ticket with the finding's detail (affected pages, technical details) included, not just change requests.
This is one-directional
There's currently no sync back from Jira/GitHub/etc into Destiny Manage - closing or completing the exported issue on the tracker side doesn't change the change request's status here. You still update the request's status in Destiny Manage yourself when the work is done.