1. Docs
  2. Administration
  3. Integrations
  4. Jira & Azure DevOps

Jira and Azure DevOps

Both integrations turn SmartestQA tasks into tickets in your tracker and bring their status back. Azure DevOps can also receive every pipeline run as a Test Plans test run.

9 min read Updated CustomersAdmins

In short

On this page you can

  • Create a Jira issue or Azure DevOps work item for every SmartestQA task.
  • Bring status, priority and assignee back from the tracker into the task.
  • Map each task status and severity to the tracker’s own values.
  • Run the sync on a timer, or with Send to Jira and Get from Jira.
  • Write each pipeline run to Azure DevOps Test Plans as an automated test run.

How to use it

  1. Create an API token (Jira Cloud) or a personal access token (Jira Server, Azure DevOps).
  2. Open the card, click Setup, paste the address and token, then Test Connection.
  3. Pick the project, issue or work item type and defaults, then the sync directions.
  4. Check the status and priority mappings, then Save.
  5. Create a test task and confirm the ticket appears in the tracker.

SmartestQA calls defects tasks. A task is created by hand, from a failed test, or by an AI agent. With Jira or Azure DevOps connected, each task gets a twin ticket, and changes made by developers in the tracker flow back.

JiraAzure DevOps
New task → ticketAt once, when the task is savedOn the next timed sync or Send tasks to Azure DevOps
Comes backStatus, priority, assignee, comments, attachment linksState and assignee
New tickets come in as tasksYes, the 200 newest unlinked issuesNo
Timed sync1 to 24 hours15 minutes to 24 hours
Test resultsNoTest Plans test runs
Remove from the pageNo (switch it off)Remove

Jira#

Before you start#

JiraAuthentication TypeWhat you enter
Jira CloudAPI Token (Jira Cloud)Your Atlassian email in Username / Email and an API token from Atlassian account › Security › API tokens.
Jira Server / Data CenterPersonal Access Token (Server/DC)A personal access token from your Jira profile. Username / Email must still be filled to enable the test button.
Jira Server, older setupsBasic AuthenticationUsername, and the password in the API Token field.

The Jira user needs permission to browse the project, create and edit issues, transition them, comment and add attachments. Use a technical user, not a person.

Set up Jira#

  1. Open the wizard

    Go to IntegrationsJira and click Setup (or Configure Now). The Jira Integration Configuration dialog has four steps.

  2. Connection Settings

    Enter Jira URL (for example https://your-company.atlassian.net), pick the Authentication Type, fill Username / Email and API Token, then click Test Connection.

    A green chip Connected: your Jira name appears. Next only works after a successful test.

  3. Project Selection

    Choose the Jira Project. The lists for Default Issue Type, Default Priority and Default Status load from that project; Bug and Medium are preselected when they exist.

  4. Sync Settings

    Under Sync Direction keep Send Tasks to Jira and Get Updates from Jira on, or turn one off. Under Automatic Synchronization, Enable Auto Sync and pick a Sync Interval of 1, 2, 4, 6, 12 or 24 hours.

  5. Field Mapping and save

    Check Severity → Priority Mapping and Status Mapping, then click Save.

    The page shows Active, the page tests the connection and shows Last test: OK.

What is sent and when#

TriggerWhat happens in JiraNeeds
A task is createdA new issue of the default type: summary is the task’s ID in square brackets plus its name; labels smartestqa and auto-synced; description with the task’s details; then the issue is moved to the mapped status, and comments and attachments are added.Integration Active and Send Tasks to Jira. Auto sync is not needed.
A linked task is changedSummary, description and priority of the issue are overwritten; the status is moved if the mapped status changed; new comments and attachments are added.Same
Send to JiraEvery task of the project is sent: new ones are created, linked ones updated.Same
Get from JiraLinked issues: status, priority and assignee overwrite the task when they differ; new comments are copied (except those SmartestQA posted); new attachments are added as links. Then the 200 newest unlinked issues of the project, of any type, become new tasks.Get Updates from Jira
Timed syncFirst Send, then Get, for each project whose interval has passed.Automatic Synchronization on

Get from Jira imports more than bugs

The first Get from Jira turns up to 200 of the project’s newest issues into tasks, whatever their type: stories and epics too. Connect a Jira project that holds only the issues you want as tasks, or turn Get Updates from Jira off before the first sync.

The last write wins

There is no conflict check. A task edit overwrites the issue summary and description; an incoming sync overwrites the task’s status, priority and assignee. Agree on where each field is edited: usually the description in SmartestQA and the status in Jira.

Status and priority mapping#

The wizard’s last step and the Configuration Summary panel on the page hold three groups. Edits on the page show the Unsaved changes bar; click Save.

GroupDefaultUsed for
Defaults: Default Issue Type, Default Priority, Default StatusBug, Medium, the project’s first statusNew issues; the default status when a task status has no mapping
Severity → Priority MappingCritical → Highest, High → High, Medium → Medium, Low → LowOutgoing priority; read backwards for incoming priority
Status MappingOpen → To Do, In Progress → In Progress, Resolved → Done, Closed → DoneOutgoing transition; read backwards for incoming status

The status rows are your company’s task statuses. Incoming Jira statuses first look for a row mapped to that Jira status. With no match, To Do, Open and Backlog become Open; In Progress and In Development become In progress; Done, Closed and Resolved become Resolved; anything else becomes Open. When two rows map to the same Jira status (Resolved and Closed both to Done by default), an incoming Done takes the first of them. The priority works the same way; Highest and Blocker become Critical, Lowest becomes Low.

Outgoing status changes move the issue through a Jira transition whose name matches the mapped status. If your workflow has no such transition, the status stays as it is.

The Jira page#

  • Linked Tasks and Successful Syncs with Last Sync. See how they are counted.
  • Connection Status: the Integration Active switch (saved at once), Jira URL, Project Key, Authentication Type, Sync Direction.
  • Synchronization: Automatic Synchronization, Sync Interval, Send to Jira, Get from Jira. Hidden with “Enable integration to use synchronization” while the switch is off.
  • Configuration Summary: defaults and mappings, edited in place.

Jira has no Remove button. Turn Integration Active off to stop it; links between tasks and issues are kept for when you turn it on again.

Azure DevOps#

Before you start#

  • A personal access token. In Azure DevOps create a token with these scopes: Work Items (read & write), Test Management (read & write), Project and Team (read). Without Test Management you can still sync tasks, but runs cannot be published.
  • The address. Azure DevOps Services: https://dev.azure.com/your-org. Azure DevOps Server: the collection URL, for example https://tfs.company.local/tfs/DefaultCollection.
  • The API version. 7.0 by default; 7.1 and 6.0 are offered. Use 6.0 for Azure DevOps Server 2020.

Set up Azure DevOps#

  1. Open the settings

    Go to IntegrationsAzure DevOps and click Setup. The Azure DevOps settings dialog opens.

  2. Connect

    Pick the Deployment: Azure DevOps Services (cloud) or Azure DevOps Server (on-premises). Enter the Organization URL or Collection URL, the Personal access token and the API version. Click Test Connection.

    “Connected to project”, and the project, type, area, iteration and plan lists fill in.

  3. Choose where work items go

    Pick the Project, the Work item type for tasks (Bug by default), and optionally the Area path and Iteration path. You can also type values the lists do not show.

  4. Choose the directions

    Keep Integration active on. Turn on Create and update work items from SmartestQA tasks and Read state and assignee back from Azure DevOps as needed. For results, turn on Publish pipeline results to Test Plans as test runs and pick a Test plan or No plan (standalone run).

  5. Save, then set the timer and mappings on the page

    Click Save. On the page, turn on Automatic Synchronization, pick a Sync Interval (15, 30 or 60 minutes, or 2, 4, 12 or 24 hours), check the Field mapping, and click Save in the Unsaved changes bar.

What is sent and when#

TriggerWhat happens
Timed sync, or Send tasks to Azure DevOpsEach task that changed since its last sync is sent. New ones become work items titled [SmartestQA-id] name with the tag SmartestQA. Bugs get the details in Repro Steps, other types in Description. Up to 10 attachments per sync, each up to 60 MB. Closed tasks that were never linked are skipped.
Timed sync, or Get updates from Azure DevOpsFor each linked work item, the state and the assignee come back. A state with no mapping and no known name is left as it is. A deleted work item is marked not found and counted under Sync problems.
A pipeline finishes (passed or failed)With Publish runs on, one automated test run named SmartestQA · pipeline · run id with one result per test case: Passed, Failed or NotExecuted. Each run is written once.

Creating a task does not create the work item at once. It goes out with the next timed sync, which runs every 5 minutes and picks the projects whose own interval has passed, or when you click the button.

Field mapping#

  • Status Mapping: for each task status, the Azure DevOps state to write, or Don't write. A status is written only when it is mapped and has changed. Incoming states use this mapping first, then the state name: New → Open, Active → In progress, Resolved, Closed or Done.
  • Priority mapping (1 = highest): Critical → 1, High → 2, Medium → 3, Low → 4 by default.

Test Plans runs#

The Test Plans panel has the Publish runs switch, the Test plan and the last 20 published runs with Pipeline, Results, Status, Open run and, for failed writes, Retry. If Azure DevOps rejects the plan, the run is written without a plan. A run with no test case results is skipped with “No test case results in this run”.

Remove#

Remove asks “Remove Azure DevOps integration?”: settings and the saved token are deleted for this project. Work items in Azure DevOps are not changed.

Best practices#

Do

  • Connect a Jira project or area path used only for test findings.
  • Map every task status you use before the first sync.
  • Create one task by hand first and check the ticket.
  • Use a technical user’s token and note when it expires.

Don’t

  • Run Get from Jira on a large shared project.
  • Edit the same field on both sides.
  • Connect two SmartestQA projects to the same tracker project unless both should see every issue.

If something goes wrong#

Didn’t find your answer?Write to support with your project name and what you see on screen.

info@smartestqa.ai
© 2026 Selenity Technology · SmartestQAsmartestqa.aiThis page as MarkdownChecked against smarttest-fe predev 2a8c79cc, smarttest-be 633c2a03 (JiraSyncService, JiraSyncScheduler, AzureDevOpsSyncService, AzureDevOpsTestRunPublisher), JIRA_INTEGRATION.md (outdated in places)