Prefer env vars at build time (GOOGLE_SITE_VERIFICATION, BING_SITE_VERIFICATION, YANDEX_VERIFICATION, BAIDU_SITE_VERIFICATION, NAVER_SITE_VERIFICATION). Optionally paste meta tags below this comment for a one-off deploy. DNS TXT alternatives: see docs/indexing-playbook.md --> Jira Service Management | Robomap Docs
Robomap Docs
Open app

Robomap Docs

Jira Service Management

Create Jira Service Management requests from Robomap device and agriculture alerts.

What it does

Connect Atlassian Cloud Jira Service Management (Service Desk) to create customer requests from device alerts or service requests, store linked issue keys, and refresh status in Robomap.

Get Atlassian credentials

  1. Sign in to your Atlassian Cloud site (for example https://your-domain.atlassian.net).
  2. Create an API token at Atlassian API tokens.
  3. Use an account email with Service Desk agent or admin access.

Connect in Robomap

  1. Go to Account → Integrations → Jira Service Desk.
  2. Enter site URL, email, and API token → Connect. Credentials are stored encrypted.
  3. Pick a service desk and request type.
  4. Optionally enable Auto-create on alerts.
  5. Create a request manually, or let auto-create run when device / agriculture / service-request alerts fire.
  6. Use Refresh on a linked issue to poll status from Jira.

Troubleshooting

  • Connect fails — verify the site URL, email, and token; confirm the user can access Jira Service Management.
  • Empty request types — select the service desk first, then refresh the request type list.
  • No auto-created issues — enable auto-create, trigger a test alert, and confirm the request type fields accept Robomap’s summary/description.