Tools
Power Automate Templates
Auto Tag DevOps Tickets into Emails

Auto Tag DevOps Tickets into Emails

Introduction

This Power Automate flow template designed to streamline the process of tagging DevOps tickets into emails. By automating this task, the flow helps improve efficiency and ensures consistent communication. It includes:

  • A downloadable Power Platform solution for rapid deployment and experimentation.
  • The Legacy Power Automate flow as a ready-to-import ZIP file.

For more information, visit the TechTweedie Blog.

Prerequisites

To use this repository, you need:

  • Access to a Power Platform environment.
  • A Power Automate account.

Obtaining Credentials

Ensure you have the necessary permissions and credentials to import solutions and flows into your Power Platform environment. Additionally, ensure you have the required permissions in DevOps to comment on work items. For more details, refer to the Power Platform documentation.

Supported Operations

Power Platform Solution

  • Import managed or unmanaged solutions into your Power Platform environment.

Power Automate Flow

  • Import and configure the legacy flow for automating DevOps ticket tagging.

Parameters

Power Automate Flow Parameters

  • Connections: Ensure all required connections are reconfigured after importing the flow.

  • DevOps URL: Update the URL to reflect your DevOps organization and project.

Using the Connector

Download the Solution

  1. Navigate to the /solutions/ folder.

  2. Download the latest solution ZIP file (choose managed or unmanaged as needed).

  3. Import the solution into your Power Platform environment via the Power Apps Maker Portal.

Import the Power Automate Flow

  1. Go to the /flows/ folder.

  2. Download the flow ZIP file.

  3. In Power Automate, select “Import” and upload the ZIP file.

  4. Reconnect any required connections.

Try it Out

Test the imported solution and flow in your Power Platform environment to ensure they work as expected. Adjust configurations as needed.

Known Issues and Limitations

  • The legacy flow may require manual reconfiguration of connections.

  • Compatibility with older Power Platform environments is not guaranteed.

License

This repository is provided under the MIT License. See the LICENSE file for details.

Contributions

Contributions are welcome! Feel free to submit issues or pull requests via the GitHub repository.

Git Repository Contents

  • /solutions/ — Contains the managed and unmanaged Power Platform solution files.

  • /flows/ — Contains the Legacy ZIP file export.

Additional Notes

This blog has been migrated from an earlier blog hosted on TechTweedie.