Skip to content
storywi.se documentation storywi.se documentation storywi.se documentation

Azure DevOps Integration

Transfer your structured requirements to Azure DevOps with a single click while maintaining complete traceability and context.

Key Features

  • One-Click Export: Transfer entire requirement sets to Azure DevOps instantly
  • Complete Context: Preserve all relationships and background information
  • Full Traceability: Maintain links between requirements and original content
  • Rich Content Transfer: Include all associated information:

    • Original requirements context

    • Mockups and screenshots

    • Effort estimates

    • Acceptance criteria

    • Related entities, stories, tasks and epics

    Note: Devops does have some limitations in the API, and some features might not work as expected, depending on the configuration of the Azure DevOps project, the permissions of the user and the configuration of the Azure DevOps instance. Please let us know if you encounter any issues.

Configure Azure DevOps Connection

  • Configure Azure DevOps Connection in the connections page
  • Add your Azure DevOps organization URL (e.g., dev.azure.com/your-organization), your project name and personal access token (PAT)

Note: this will be the user that will be used to create the work items in Azure DevOps.

  • Click on “Save and test”
  • You will get feedback on whether the connection was successful or not.

Connection possibilities

Direct Connection

With the PAT set and an Azure DevOps instance reachable from storywise, you can directly connect to Azure DevOps. If you use a self-hosted Azure DevOps Server, you need to make sure that the host is reachable from storywise (contact us if you need help with this). In the top menu in a project, you will find a “Sync” button. Clicking it will bring you to the project connection page, if you have not connected your project yet. If your project is already connected, you will be able to choose which content you want to sync to Azure DevOps.

Sync Mode: You’ll be able to choose between:

  • Only new content: Only synchronizes epics/stories/tasks that have been created since the last synchronization to Azure DevOps.
  • New content and update existing: Synchronizes new epics/stories/tasks created since the last sync and updates content of existing items - like descriptions, acceptance criteria, screens and links.
  • Delete and resync all: Deletes all previously synchronized stories and transfers them again completely.

Note: If you choose to delete and resync all, storywise will still only delete and recreate work items that were created in storywise.

Note 2: If you have deleted work items in Azure DevOps, you need to do a manual deletion in storywise to delete them.

Epic Options:

Now you can choose which epics you want to sync to Azure DevOps.

Features and Releases:

You can choose for each feature and release if you want to sync it to Azure DevOps. This is the same status as in the pricing and export page. storywise will remember the last choice, if saved, so you get the same result as in the pricing and export page. However, you can override the status without saving the choice if you want to, for example if you want to export a feature without syncing it to Azure DevOps. storywise will also remember who saved the choice.

Safety questions:

You will be asked to confirm the sync if you are choosing to delete and resync all and see the list of epics that will be deleted and recreated.

How to get an Azure DevOps Personal Access Token

Follow these steps to create your token:

  1. Log in to your Azure DevOps account
  2. Click on your avatar and select “Security” from the menu
  3. Click on “Personal Access Tokens”
  4. Click on “New Token”
  5. Enter a name for the token and select the permissions

Note: You need to select the permissions “Work Items (read and write)” and “Project and team (read and write)”

  1. Click on “Create”
  2. Copy the created token and paste it into storywise

Note: This is the only opportunity to copy the token. Otherwise, you will need to create a new token.