Duaer

App recipes

Sync new Jira issues to GitHub issues with Duaer

In Duaer, each new Jira issue opens a matching GitHub issue, and the GitHub link goes back to Jira as a comment.

Build the sync in Duaer

  1. Create Jira credentials and GitHub credentials. Jira Trigger needs Jira admin rights to register its webhook.
  2. Add Jira Trigger with Events Issue Created.
  3. To sync only some issues, add If, such as {{ $json.issue.fields.labels.includes("github") }}.
  4. Add GitHub with Resource Issue and Operation Create, plus Repository Owner and Repository Name. Title: [{{ $json.issue.key }}] {{ $json.issue.fields.summary }}; Body: the description and https://your-site.atlassian.net/browse/{{ $json.issue.key }}.
  5. Add Jira with Resource Issue Comment, Operation Add, Issue Key {{ $('Jira Trigger').item.json.issue.key }}, Comment {{ $json.html_url }}.
  6. Publish the digital organization.

Keep in mind

  • Jira descriptions use Jira markup, so formatting shifts on GitHub. Keep key facts in the title or the link back.
  • This flow is one way. For two-way sync, build a second digital organization from GitHub Trigger and use the Jira key in the title to avoid loops.

Questions

Can Duaer sync Jira and GitHub both ways?

Yes, with two Duaer digital organizations, one per direction, using the Jira key in the title to avoid loops.

Why does Duaer Jira Trigger fail to register?

Registering a Jira webhook needs admin rights. Use a Jira admin credential, or ask an admin to add the Duaer webhook URL in Jira.

In this section