Use the Jira handoff when your team wants reviewed Sensra tasks created as issues in an existing Jira project.
What Sensra sends
Sensra creates Jira issues in the site, project, and issue type you choose. Sensra sends reviewed task details only, such as task title, description, phase, priority, delivery status, due date, Done means, owner/suggested owner label, and source section label.
Sensra does not send comments, client responses, source excerpts, AI drafts, internal rationale, files, public links, tokens, or private project history.
This is a one-way handoff. Sensra does not sync changes back from the PM tool, and it does not update external tasks after they are created.
Before you connect
- Choose the Jira site and project that should receive approved tasks.
- Make sure the Atlassian account you connect can create issues in that project.
- Choose an issue type with required fields Sensra can fill. Standard task-like issue types usually work best.
Atlassian's OAuth 2.0 authorization guide explains the authorization flow, and its create issue reference covers the issue creation endpoint Sensra uses.
Connect Jira in Sensra
- Open a Sensra project and go to Overview.
- Open Project tools, then open Send to PM tool.
- Select Jira and choose Connect Jira.
- Complete the Atlassian authorization screen and return to Sensra.
- Choose the Jira site, project, and issue type in the handoff panel.
After authorization, Sensra stores the connected app securely. You choose and validate the Jira destination from the handoff panel before previewing or sending tasks.
Run the handoff
- Approve the tasks you want to send.
- Choose a Jira site, project, and compatible issue type.
- Preview approved tasks from the PM handoff panel.
- Review the count of tasks that will send and tasks already sent.
- Select Send approved tasks to Jira.
Sensra creates Jira issues with the reviewed task title and details. Sensra validates the selected issue type before handoff and blocks issue types with required fields Sensra cannot fill yet. Sensra does not create comments, attachments, dependencies, sprints, or two-way status sync.
Duplicate and skipped tasks
If a task was already sent to Jira from this project handoff connection, Sensra marks it as already sent and skips it on later runs. The result summary shows created, skipped, and failed counts.
Disconnect Jira
Open the PM handoff panel, select Jira, and choose Disconnect. This removes the saved Sensra connection. It does not delete Jira issues that were already created.
Troubleshooting
- Connection failed: Reconnect Jira and confirm the Atlassian account can access the destination site and project.
- Destination required: Choose a Jira site, project, and issue type before previewing or sending.
- Unsupported issue type: Choose another issue type or update the Jira field configuration so Sensra can create issues without extra required fields.
- No tasks to send: Approve at least one task in Sensra first.
- Tasks are skipped: Skipped tasks were already handed off from this connection.