Skip to main content
Use Jira delivery when a saved capture should enter a Jira project. A workspace owner connects one Jira site and project. Members use the configured project; owners can choose an accessible project exposed by the selected site when sending.

​
Requirements and connection

You need a workspace owner for setup and capture editing permission to send. Tekma uses the Jira Cloud REST v3 surface. OAuth requires a deployment-configured client and may authorize more than one Jira site. A token connection needs an HTTPS Site URL, Account email, a Project key, and optionally a default Issue type. The credential must be able to read create metadata and create issues.
  1. Open Settings → Integrations and choose Connect next to Jira.
  2. Choose Continue to Jira for OAuth, or choose Use a token instead and enter the token and account email.
  3. For a token connection, enter Site URL, Account email, Project key, and optional Issue type. For OAuth covering multiple sites, choose the intended Jira site in Manage; changing the site clears the project.
  4. Choose Connect Jira or Save destination. Tekma verifies the site/project before marking the row Connected.
Use Manage to select another granted site or edit the destination while retaining OAuth credentials. Disconnecting Tekma does not revoke a token in Jira.

​
Send an issue

  1. Open a saved capture and choose Send to app → Jira.
  2. Wait for Loading preview… and review the site, project, issue type, title, description and private capture link.
  3. Select Project, Issue type, Priority, Labels, Components, Versions, Due date, Environment, and supported custom fields when Jira exposes them in create metadata. Custom values may be text, multiline text, number, date, single option, or multiple options. Tekma does not show an assignee/reporter user picker, cascading options, subtasks, or arbitrary app-defined field types.
  4. Use Edit visible fields to hide optional controls, add context, then choose Send to Jira.
  5. Open the returned issue in Jira and confirm the fields. If delivery was not confirmed, inspect Jira before retrying.
The issue receives saved description, optional context, sanitized source URL, capture kind and a private Tekma link. It does not receive media, comments, network logs, or console payloads. A required Jira field of an unsupported type, with no provider default, blocks the send rather than being silently omitted.

​
Troubleshooting

If OAuth sites do not load, reconnect or inspect whether the grant includes the Jira site and the required scopes. For token connections, use a full HTTPS URL and a valid account email. Reopen the preview after changing project or issue type because metadata is destination-specific. If Jira says a required field is missing, choose a supported value or use an issue type whose create scheme can be satisfied. A timeout can follow a successful create; search Jira by title before sending again.