Sign In

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

  1. Navigate to Settings > Integrations in your Buildorado dashboard.
  2. Find Jira and click Connect.
  3. Sign in with your Atlassian account in the authorization popup.
  4. Select the Jira site (e.g., yourteam.atlassian.net) you want to connect.
  5. Grant the requested permissions:
    • read:jira-work -- Read project and issue data
    • write:jira-work -- Create and update issues
    • read:jira-user -- Read user information for assignees
  6. Once authorized, Jira shows as Connected with your site name.

Operations

createIssue

Create a new issue in a Jira project.

FieldTypeRequiredDescription
projectKeystringYesThe Jira project key (e.g., BUG, FEAT, SUP)
issueTypeselectYesIssue type: Task, Bug, Story, or Epic
summarystringYesIssue title / summary
descriptionstringNoDetailed description
priorityselectNoHighest, High, Medium, Low, or Lowest
assigneestringNoAtlassian account ID of the assignee
labelsstringNoLabels to apply (comma-separated)

Output:

FieldTypeDescription
idstringThe issue ID
keystringThe issue key (e.g., BUG-142)
selfstringAPI URL to the created issue

updateIssue

Update an existing Jira issue.

FieldTypeRequiredDescription
issueKeystringYesThe issue key (e.g., PROJ-123)
summarystringNoUpdated issue title
descriptionstringNoUpdated description
statusstringNoTransition name (e.g., Done, In Progress)
assigneestringNoAtlassian account ID of the new assignee

Output:

FieldTypeDescription
keystringThe issue key

addComment

Add a comment to a Jira issue.

FieldTypeRequiredDescription
issueKeystringYesThe issue key (e.g., PROJ-123)
bodystringYesComment body

Output:

FieldTypeDescription
idstringThe comment ID
createdstringComment creation timestamp

Field Mapping Example

Form Field                   Jira Field
------                       ------
{{form.title}}            -- summary
{{form.description}}      -- description
{{form.priority}}         -- priority
"BUG"                     -- projectKey
"Bug"                     -- issueType

Description 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 key output 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

  1. Navigate to Settings > Integrations and click Connect next to Azure DevOps.
  2. Sign in with your Microsoft account in the authorization popup.
  3. Select the Azure DevOps organization and project you want to connect.
  4. Grant the requested permissions for work item read and write access.
  5. Once authorized, Azure DevOps shows as Connected.

Operations

createWorkItem

Create a new work item (Task) in an Azure DevOps project.

FieldTypeRequiredDescription
organizationstringYesAzure DevOps organization name
projectstringYesProject name or ID
titlestringYesWork item title
descriptionstringNoWork item description
assignedTostringNoEmail of the assigned user

Output:

FieldTypeDescription
idnumberThe numeric ID of the created work item
urlstringDirect URL to the work item
fieldsstringWork item fields as JSON

listWorkItems

Query work items using WIQL (Work Item Query Language).

FieldTypeRequiredDescription
organizationstringYesAzure DevOps organization name
querystringYesWIQL query string

Output:

FieldTypeDescription
workItemsstringWork items as JSON

listProjects

Get a list of projects in the Azure DevOps organization.

FieldTypeRequiredDescription
organizationstringYesAzure DevOps organization name

Output:

FieldTypeDescription
projectsstringProjects as JSON

Tips for Azure DevOps

  • The organization field 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

  1. Navigate to Settings > Integrations and click Connect next to Microsoft Planner.
  2. Sign in with your Microsoft 365 account.
  3. Grant permissions for reading and writing Planner tasks and plans. The following scopes are requested:
    • User.Read -- Read your profile
    • Tasks.ReadWrite -- Create and manage tasks
    • Group.ReadWrite.All -- Access group plans
    • offline_access -- Maintain the connection
  4. Once authorized, Planner shows as Connected.

Operations

createTask

Create a new task in a Microsoft Planner plan.

FieldTypeRequiredDescription
planIdstringYesThe Planner plan ID
titlestringYesTask title
bucketIdstringNoBucket ID to place the task in
dueDateTimedatetimeNoDue date in ISO 8601 format
assignmentsstringNoJSON object mapping user IDs to assignments

Output:

FieldTypeDescription
idstringThe Planner task ID
titlestringThe task title
planIdstringThe plan ID
bucketIdstringThe bucket ID
createdDateTimestringWhen the task was created

listTasks

List tasks in a Microsoft Planner plan.

FieldTypeRequiredDescription
planIdstringYesThe Planner plan ID

Output:

FieldTypeDescription
tasksstringTasks as JSON

listPlans

List Microsoft Planner plans for the current user. This operation takes no input fields.

Output:

FieldTypeDescription
plansstringPlans 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

  1. Navigate to Settings > Integrations and click Connect next to Microsoft To Do.
  2. Sign in with your Microsoft 365 account.
  3. Grant permissions for task read and write access. The following scopes are requested:
    • User.Read -- Read your profile
    • Tasks.ReadWrite -- Create and manage tasks
    • offline_access -- Maintain the connection
  4. Once authorized, To Do shows as Connected.

Operations

createTask

Create a new task in a Microsoft To Do list.

FieldTypeRequiredDescription
listIdstringYesThe To Do list ID
titlestringYesTask title
bodystringNoTask notes (optional)
importanceselectNolow, normal, or high
dueDateTimedatetimeNoDue date in ISO 8601 format
reminderDateTimedatetimeNoReminder date and time

Output:

FieldTypeDescription
idstringThe task ID
titlestringThe task title
statusstringThe task status
createdDateTimestringWhen the task was created

listTasks

Get tasks from a Microsoft To Do list.

FieldTypeRequiredDescription
listIdstringYesThe To Do list ID
topnumberNoNumber of tasks to return

Output:

FieldTypeDescription
tasksstringTasks as JSON

listTaskLists

Get all Microsoft To Do task lists. This operation takes no input fields.

Output:

FieldTypeDescription
taskListsstringTask 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 listTaskLists operation 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

  1. Navigate to Settings > Integrations and click Connect next to Microsoft Forms.
  2. Sign in with your Microsoft 365 account.
  3. Grant the requested permissions:
    • User.Read -- Read your profile
    • offline_access -- Maintain the connection
  4. Once authorized, Microsoft Forms shows as Connected.

Operations

OperationDescription
listFormsRetrieve a list of forms owned by the current user
getResponsesFetch 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.

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.

On this page

Project Management Integrations | Buildorado