Create a Jira Cloud issue for each accepted submission.
Availability: awaiting provider verification. The connector is built and tested against recorded responses, but it has not yet passed a live test in a Jira site, so it is off by default and shown as "Implemented, awaiting provider verification". Jira Cloud only; self-hosted Jira is not supported. Sign-in with Atlassian OAuth and status sync are not available yet.
What you need
- A Jira Cloud site (
yoursite.atlassian.net). - An Atlassian API token from an account that can create issues in the project.
- The project key.
What you configure
- Site, account email and API token.
- Project key and issue type - defaults to
Task; the type must exist in the project. - Title field - defaults to
name; falls back to the form name and submission id.
What Formspring sends
An issue with the title above as its summary and a description listing the answers in a code block, followed by a line naming the form and submission it came from.
Steps
- At id.atlassian.com, open Security → API tokens and create a token.
- In Formspring, open your form → Integrations → Jira → fill the fields → Save.
- Submit a test and confirm the issue and a 2xx in Deliveries.
Tips
- If Jira rejects the request, for example a missing permission or issue type, the delivery log shows the status. Fix it in Jira and use Replay.
- Jira rate limits return a wait time; a limited delivery is retried automatically.
