Troubleshooting
Jira issue not created
When Jira is connected, a delivery's issue goes to the first that applies: what was named
(jira: KEY or jira: KEY-12, or the portal form's Jira fields), then the project mapped to one
of its repos, then the project mapped to its Slack channel, then the default project. If none is
set, the project doesn't exist, or Jira errors, the delivery says why in its thread and activity
feed and carries on without one. An existing issue is only linked if Jira can see it. Fix it in
Integrations → Jira (default project, per-repo and per-channel rows). A delivery split per repo
gets one issue per repo.