Configure DevOps Work Item Form for TekStack Help Desk Integration
Creation and update of DevOps Bugs between Dataverse and DevOps is handled by Power Automate flows that are triggered by field actions in either TekStack Help Desk or Azure DevOps.
The fields in DevOps that trigger the Power Automate flows for the integration must be manually added to the corresponding Work Item in DevOps.
/msdyn_blobfile/$value)
/msdyn_blobfile/$value)
Create a NEW process that is a clone of your active process to make the configurations. The NEW process can then be applied to a TEST project for verification prior to updating your live project. Instructions on how to do this are included in this article.
For more information on Inherited Processes and how to create them, see Create inherited process.
/msdyn_blobfile/$value)
/msdyn_blobfile/$value)
/msdyn_blobfile/$value)
/msdyn_blobfile/$value)
Dataverse Id
The Guid identifier of the work item in Dataverse.
/msdyn_blobfile/$value)
Sync with Dataverse
Indicates if the work item should be synced to Dataverse. Work items created from Dataverse with have Sync with Dataverse = true.
/msdyn_blobfile/$value)
Dataverse URL
URL link to the synced work item in Dataverse.
/msdyn_blobfile/$value)
Repro Steps
How to see the bug. End by contrasting expected with actual behavior.
/msdyn_blobfile/$value)
/msdyn_blobfile/$value)
/msdyn_blobfile/$value)
/msdyn_blobfile/$value)
/msdyn_blobfile/$value)
/msdyn_blobfile/$value)
/msdyn_blobfile/$value)
/msdyn_blobfile/$value)
Now, Bugs in your team’s active project will have the configured fields for the TekStack integration.
Background
TekStack has an integration between TekStack Help Desk (Dataverse) and Azure DevOps. Today, we support one use case: synchronizing DevOps Bugs and relating them to TekStack Cases. New DevOps Bugs can be created from a Case. Previously created DevOps Bugs can be linked to other Cases. Existing Bugs in Azure DevOps can be synced to TekStack.Creation and update of DevOps Bugs between Dataverse and DevOps is handled by Power Automate flows that are triggered by field actions in either TekStack Help Desk or Azure DevOps.
The fields in DevOps that trigger the Power Automate flows for the integration must be manually added to the corresponding Work Item in DevOps.
DevOps Work Item Type Configuration
Prerequisites
- Organization requirement: Ensure you have an organization in Azure DevOps.
- Permissions:
- Be a member of the Project Collection Administrators group.
- Have collection-level permissions such as Create process, Delete process, Edit process, or Delete a field from organization set to Allow.
- These permissions allow you to modify processes and fields within your organization.
Add Custom Fields to a Work Item Type
- Sign in to your organization (https://dev.azure.com/{yourorganization})
- Select
Organization settings.
- Select Process.
Create a NEW process that is a clone of your active process to make the configurations. The NEW process can then be applied to a TEST project for verification prior to updating your live project. Instructions on how to do this are included in this article.
For more information on Inherited Processes and how to create them, see Create inherited process.
Add a Field
Do the following steps to add a field to an existing Work Item Type (WIT). The preferred WIT to use for the TekStack integration is Bug.- From the Process page of the selected inherited process, choose the Bug work item type.
- With the WIT selected, choose
New field.
- Name the field, select the field type and add the description exactly as depicted in the following screen shots.
- On the Layout tab of the Dataverse fields, select “Create new group” and name the group “Dataverse.” This will place the Dataverse fields in their own section on the Bug form. It will end up looking like this:
- The Repro Steps field can be added to an existing group or placed into a new group. Here’s an example of the Repro Steps field placed underneath the Description field on the Bug form:
Dataverse Id
The Guid identifier of the work item in Dataverse.
Sync with Dataverse
Indicates if the work item should be synced to Dataverse. Work items created from Dataverse with have Sync with Dataverse = true.
Dataverse URL
URL link to the synced work item in Dataverse.
Repro Steps
How to see the bug. End by contrasting expected with actual behavior.
Verify your Configurations
Verify with a Test Project
We recommend that you create a test project and apply your customized inherited process to it to verify the changes you've made.- Open the All processes page and choose the … context menu for the process you want to use, and then select New team project.
- The Create new project page opens. Fill out the form.
- Open Work Items. (1) Check that you have selected the right project, then (2) choose Work>Work Items.
- Select the WIT you customized – Bug.
- Verify that the field you added appears on the form. Note that the
(exclamation mark) icon indicates the field is required. The 4 fields added for the TekStack integration are not required. If they are showing as required, edit the fields and adjust the field requirement settings in the Options tab.
Apply the Customized Process to your Project
After you've verified your customizations, you can now apply the process to your active team project.- Select the new process with the field configurations.
- Open the … context menu for the project you want to change and choose the Change process option.
- From the Change the project process dialog, choose the new process from the menu of options. And, then choose Save.
Now, Bugs in your team’s active project will have the configured fields for the TekStack integration.