Escalate a GitHub issue to Jira once, linked both ways

**Objective:** Create a Jira issue in project `{project-key}` for GitHub issue number `{issue-number}` in repository `{repository}` (if blank, use the connector's default repository), link it back to GitHub, and note the Jira key on the GitHub issue.

**Step 1: Read the GitHub issue**

Call `github-get-issue` with `issue-number` set to `{issue-number}` (pass `company` = `{repository}` when given). If nothing comes back, report that the issue does not exist and stop. Note the title, body, labels, assignee and issue-url.

**Step 2: Check it has not already been escalated**

Call `jira-get-issue-remote-link` with `global-id` set to the GitHub issue-url. If a link exists, report that the issue is already linked from Jira and stop. Also call `jira-get-issue` with `project-key` = `{project-key}` and `summary.contains` set to the GitHub title; list any close matches and ask the user whether to continue.

**Step 3: Resolve the Jira ids**

1. Call `jira-get-project` with `project-key` = `{project-key}` and take `project-id`.
2. Call `jira-get-issue-type` with `project-key` = `{project-key}` and `name` = `{issue-type}` (default Bug) and take `issue-type-id`. If there is no match, list the project's issue types and ask.

**Step 4: Confirm**

Show the user the Jira summary (the GitHub title followed by the GitHub issue number, for example Login fails on Safari (GitHub #42)), project and issue type, and wait for an explicit yes.

**Step 5: Write**

1. Call `jira-add-issue` with `project-id`, `issue-type-id` and `summary`. Do not set an assignee; GitHub logins do not map to Jira accounts.
2. Take the new issue's key and id from the response. If the id is missing, call `jira-get-issue-watcher` with `issue-key` set to the new key and take `issue-id`.
3. Call `jira-add-issue-remote-link` with that `issue-id`, `url` and `global-id` both set to the GitHub issue-url, `title` set to the GitHub title, `application-name` GitHub and `relationship` relates to.
4. Call `github-add-issue-comment` on `{issue-number}` with the body: Tracked in Jira as the new key.

**Step 6: Report**

The Jira key, the GitHub issue-url, and which of the three writes succeeded.

**Rules & Guidelines:**

* Tools whose names start with jira- are on the jira server; tools whose names start with github- are on the github server.
* Make exactly one `jira-add-issue` call, and only after the Step 4 yes. Do NOT call `github-update-issue` to close or relabel the GitHub issue.
* The GitHub body is not copied: `jira-add-issue` takes no description. Say so in the report.

**Validation:**

* If the remote link or GitHub comment fails after the Jira issue was created, do not create the issue again. Report the Jira key and the step that failed.
* If no `issue-id` can be resolved, skip the remote link, report the Jira key, and ask the user to link it by hand.