Project Management Integrations
Create issues, tasks, and work items in Jira, Azure DevOps, Microsoft Planner, Microsoft To Do, and Microsoft Forms from your Buildorado workflows.
Project management integrations bridge the gap between user-facing forms and your team's internal task tracking tools. When a user submits a bug report, feature request, support ticket, or internal request through a Buildorado form, the integration automatically creates an issue, task, or work item in your project management platform with all the submitted data pre-populated. This eliminates manual data entry and ensures nothing falls through the cracks.
Jira (Coming Soon)
Jira by Atlassian is the most popular project management tool for software teams. The Buildorado integration will let you create and update issues in any Jira project from your workflows. This integration is currently in development and will be available in an upcoming release.
Setting Up Jira
- Navigate to Settings > Integrations in your Buildorado dashboard.
- Find Jira and click Connect.
- Sign in with your Atlassian account in the authorization popup.
- Select the Jira site (e.g.,
yourteam.atlassian.net) you want to connect. - Grant the requested permissions:
read:jira-work-- Read project and issue datawrite:jira-work-- Create and update issuesread:jira-user-- Read user information for assignees
- Once authorized, Jira shows as Connected with your site name.
Operations
createIssue
Create a new issue in a Jira project.
| Field | Type | Required | Description |
|---|---|---|---|
projectKey | string | Yes | The Jira project key (e.g., BUG, FEAT, SUP) |
issueType | select | Yes | Issue type: Task, Bug, Story, or Epic |
summary | string | Yes | Issue title / summary |
description | string | No | Detailed description |
priority | select | No | Highest, High, Medium, Low, or Lowest |
assignee | string | No | Atlassian account ID of the assignee |
labels | string | No | Labels to apply (comma-separated) |
Output:
| Field | Type | Description |
|---|---|---|
id | string | The issue ID |
key | string | The issue key (e.g., BUG-142) |
self | string | API URL to the created issue |
updateIssue
Update an existing Jira issue.
| Field | Type | Required | Description |
|---|---|---|---|
issueKey | string | Yes | The issue key (e.g., PROJ-123) |
summary | string | No | Updated issue title |
description | string | No | Updated description |
status | string | No | Transition name (e.g., Done, In Progress) |
assignee | string | No | Atlassian account ID of the new assignee |
Output:
| Field | Type | Description |
|---|---|---|
key | string | The issue key |
addComment
Add a comment to a Jira issue.
| Field | Type | Required | Description |
|---|---|---|---|
issueKey | string | Yes | The issue key (e.g., PROJ-123) |
body | string | Yes | Comment body |
Output:
| Field | Type | Description |
|---|---|---|
id | string | The comment ID |
created | string | Comment creation timestamp |
Field Mapping Example
Form Field Jira Field
------ ------
{{form.title}} -- summary
{{form.description}} -- description
{{form.priority}} -- priority
"BUG" -- projectKey
"Bug" -- issueTypeDescription Formatting
Jira uses wiki-style markup in descriptions. You can compose rich descriptions from form data:
h3. Bug Report from {{form.reporterName}}
*Environment:* {{form.environment}}
*Browser:* {{form.browser}}
*Steps to Reproduce:*
{{form.stepsToReproduce}}
*Expected Behavior:*
{{form.expectedBehavior}}
*Actual Behavior:*
{{form.actualBehavior}}
Submitted via Buildorado on {{submission.createdAt}}Common Patterns
Bug report form to Jira:
[Form: Bug Report]
-- [Jira: Create Bug issue]
-- [Slack: #engineering "New bug {{jira_1.key}}: {{form.title}}"]
-- [Email: Confirmation to {{form.reporterEmail}}]Feature request with priority routing:
[Form: Feature Request]
-- Branch: priority
-- "Critical" -- [Jira: Create Story in URGENT project]
-- else -- [Jira: Create Story in BACKLOG project]Tips for Jira
- Use the
keyoutput to create links in notification messages, e.g.,https://yourteam.atlassian.net/browse/{{jira_1.key}}. - Jira Cloud and Jira Data Center are both supported.
Azure DevOps
Azure DevOps provides work item tracking, boards, and backlogs for development teams. The Buildorado integration creates work items and queries existing ones in your Azure DevOps projects.
Setting Up Azure DevOps
- Navigate to Settings > Integrations and click Connect next to Azure DevOps.
- Sign in with your Microsoft account in the authorization popup.
- Select the Azure DevOps organization and project you want to connect.
- Grant the requested permissions for work item read and write access.
- Once authorized, Azure DevOps shows as Connected.
Operations
createWorkItem
Create a new work item (Task) in an Azure DevOps project.
| Field | Type | Required | Description |
|---|---|---|---|
organization | string | Yes | Azure DevOps organization name |
project | string | Yes | Project name or ID |
title | string | Yes | Work item title |
description | string | No | Work item description |
assignedTo | string | No | Email of the assigned user |
Output:
| Field | Type | Description |
|---|---|---|
id | number | The numeric ID of the created work item |
url | string | Direct URL to the work item |
fields | string | Work item fields as JSON |
listWorkItems
Query work items using WIQL (Work Item Query Language).
| Field | Type | Required | Description |
|---|---|---|---|
organization | string | Yes | Azure DevOps organization name |
query | string | Yes | WIQL query string |
Output:
| Field | Type | Description |
|---|---|---|
workItems | string | Work items as JSON |
listProjects
Get a list of projects in the Azure DevOps organization.
| Field | Type | Required | Description |
|---|---|---|---|
organization | string | Yes | Azure DevOps organization name |
Output:
| Field | Type | Description |
|---|---|---|
projects | string | Projects as JSON |
Tips for Azure DevOps
- The
organizationfield is required for every operation. This is your Azure DevOps organization name. - Custom fields are supported using the field reference name (e.g.,
Custom.CustomerPriority). - Use listProjects to discover project names during setup.
Microsoft Planner
Microsoft Planner is a lightweight task management tool within Microsoft 365, ideal for team collaboration and project tracking.
Setting Up Microsoft Planner
- Navigate to Settings > Integrations and click Connect next to Microsoft Planner.
- Sign in with your Microsoft 365 account.
- Grant permissions for reading and writing Planner tasks and plans. The following scopes are requested:
User.Read-- Read your profileTasks.ReadWrite-- Create and manage tasksGroup.ReadWrite.All-- Access group plansoffline_access-- Maintain the connection
- Once authorized, Planner shows as Connected.
Operations
createTask
Create a new task in a Microsoft Planner plan.
| Field | Type | Required | Description |
|---|---|---|---|
planId | string | Yes | The Planner plan ID |
title | string | Yes | Task title |
bucketId | string | No | Bucket ID to place the task in |
dueDateTime | datetime | No | Due date in ISO 8601 format |
assignments | string | No | JSON object mapping user IDs to assignments |
Output:
| Field | Type | Description |
|---|---|---|
id | string | The Planner task ID |
title | string | The task title |
planId | string | The plan ID |
bucketId | string | The bucket ID |
createdDateTime | string | When the task was created |
listTasks
List tasks in a Microsoft Planner plan.
| Field | Type | Required | Description |
|---|---|---|---|
planId | string | Yes | The Planner plan ID |
Output:
| Field | Type | Description |
|---|---|---|
tasks | string | Tasks as JSON |
listPlans
List Microsoft Planner plans for the current user. This operation takes no input fields.
Output:
| Field | Type | Description |
|---|---|---|
plans | string | Plans as JSON |
Tips for Microsoft Planner
- Plan IDs and bucket IDs can be found through the Microsoft Graph API or by inspecting the Planner URL in your browser.
- Planner tasks support checklist items, but these must be added after task creation via a separate update call.
- Assignments require Microsoft 365 user IDs (GUIDs), not email addresses. Pass them as a JSON object.
Microsoft To Do
Microsoft To Do is a personal and shared task management app. Use it for simpler task tracking that does not require full project management.
Setting Up Microsoft To Do
- Navigate to Settings > Integrations and click Connect next to Microsoft To Do.
- Sign in with your Microsoft 365 account.
- Grant permissions for task read and write access. The following scopes are requested:
User.Read-- Read your profileTasks.ReadWrite-- Create and manage tasksoffline_access-- Maintain the connection
- Once authorized, To Do shows as Connected.
Operations
createTask
Create a new task in a Microsoft To Do list.
| Field | Type | Required | Description |
|---|---|---|---|
listId | string | Yes | The To Do list ID |
title | string | Yes | Task title |
body | string | No | Task notes (optional) |
importance | select | No | low, normal, or high |
dueDateTime | datetime | No | Due date in ISO 8601 format |
reminderDateTime | datetime | No | Reminder date and time |
Output:
| Field | Type | Description |
|---|---|---|
id | string | The task ID |
title | string | The task title |
status | string | The task status |
createdDateTime | string | When the task was created |
listTasks
Get tasks from a Microsoft To Do list.
| Field | Type | Required | Description |
|---|---|---|---|
listId | string | Yes | The To Do list ID |
top | number | No | Number of tasks to return |
Output:
| Field | Type | Description |
|---|---|---|
tasks | string | Tasks as JSON |
listTaskLists
Get all Microsoft To Do task lists. This operation takes no input fields.
Output:
| Field | Type | Description |
|---|---|---|
taskLists | string | Task lists as JSON |
Tips for Microsoft To Do
- To Do integrates with Outlook Tasks. Tasks created through this integration appear in both To Do and Outlook.
- Shared lists allow team collaboration. Use a shared list ID to create tasks visible to the entire team.
- Use the
listTaskListsoperation to discover list IDs.
Microsoft Forms
Microsoft Forms integration allows you to list forms and retrieve form responses within the Microsoft 365 ecosystem.
Setting Up Microsoft Forms
- Navigate to Settings > Integrations and click Connect next to Microsoft Forms.
- Sign in with your Microsoft 365 account.
- Grant the requested permissions:
User.Read-- Read your profileoffline_access-- Maintain the connection
- Once authorized, Microsoft Forms shows as Connected.
Operations
| Operation | Description |
|---|---|
listForms | Retrieve a list of forms owned by the current user |
getResponses | Fetch responses for a specific form (requires formId) |
This integration is useful for teams that already use Microsoft Forms and want to trigger Buildorado workflows based on form responses.
Using Template Variables Across All Integrations
All project management integrations support the standard Buildorado template variable syntax. Reference any upstream form field or node output in your configuration:
Title: "[{{form.priority}}] {{form.title}}"
Description: "Reported by {{form.reporterName}} ({{form.email}}) on {{submission.createdAt}}"Best Practices
Assign Based on Form Data
Use conditional logic to route tasks to different assignees or projects based on the form submission:
[Form: Internal Request]
-- Branch: department
-- "Engineering" -- [Jira: Create in ENG project, assign to tech lead]
-- "Marketing" -- [Planner: Create in Marketing plan]
-- "HR" -- [To Do: Create in HR shared list]Include Submission Context
Always include enough context in the task description for the assignee to act on it without going back to the original form. Include the submitter's name, email, timestamp, and all relevant form fields.
Link Back to Buildorado
Include the Buildorado submission URL in the task description so assignees can view the full submission details, download attachments, and see the complete workflow execution history.
Error Handling
Attach an error handler node to catch API failures (authentication expired, required field missing, project not found) and route to a fallback action like a Slack notification or email alert.