Introduction
IriusRisk lets users integrate with some of the most popular issue trackers on the market.
This article aims to help integrate your application with your issue trackers.
Integrating with Azure Devops
Linking to issue trackers
- Navigate to settings > issue trackers
-
Configure general settings
- Sync interval – how often IriusRisk contacts the issue tracker to pull all details for that project/threat/countermeasure etc.
- Default profile – unless specified differently, what profile is set by default
- Weaknesses
- Create issue when test fail
- Close issues when test pass
-
Configure Issue Tracker Profile
- To add a new issue tracker configuration, please select ‘new
- Specify which issue tracker to configure
-
Connection with Azure Devops
- Assign a name to the new issue tracker profile.
- Configure the url.
- Configure the username
- Configure the API Token
- Configure the project name
- Assign a name to the new issue tracker profile.
- If you are using a proxy, assign the proxy details
- At this point, now is a good time to test the connection
- To add a new issue tracker configuration, please select ‘new
-
Configure Issue Workflow Status
- These need to align with the different workflow states you have assigned inside Azure Devops.
- For example, 'To Do', 'Doing', 'Done'
-
Configure Issue Field Values
- Next, we need to specify the issue field's.
- Firstly, specify the work item type
- For example, 'Task', 'Epic', 'Issue'
- For example, 'Task', 'Epic', 'Issue'
- Then we need to specify priority values
- For example, '1', '2', '3', '4'.
- For example, '1', '2', '3', '4'.
- Specify any tags and/or severity levels if used
- Test the connection and if all is fine, publish the changes
- You can now use your new issue tracking profile
Comments
0 comments
Article is closed for comments.