Integrating with, or moving from, Jira or Azure DevOps
Keep your teams in Jira or Azure DevOps and see everything above them in DelPulse, or bring all of it into DelPulse. Video ready
Watch
You will be able to
- Choose for each product: integrate, or move
- Connect Jira or Azure DevOps by API, or import an export file
- Know what DelPulse shows when teams keep working in their tool
Step by step
- Choose for each product Workspace › Tracker settings
DelPulse boards, integrate with Jira or Azure DevOps, or move from them. A network can mix all three. - Integrate by API Tracker settings › Jira or Azure DevOps › Integrate
Connect once, then link a product to its Jira project or Azure DevOps project. Both ways: work comes into DelPulse, and items created on a linked product or team, status changes and comments go to Jira or Azure DevOps too. - Teams keep working there Team › Work
Team boards and sprints stay in Jira or Azure DevOps. The team page shows the current sprint, its progress and a link to the team’s board. - Everything above the team, in DelPulse Portfolio and Product Kanban
Epics land on the organisation’s Portfolio Kanban and features on the Product Kanban. Dependencies, risks, estimates, reports, the value score and gates cover the pulled work. Sub-tasks and tasks come in as checklist items. - Or move Work › Import, or Tracker settings › Move to DelPulse boards
Import a Jira or Azure DevOps export file, or connect, pull everything once and choose Move to DelPulse boards. Every item comes with its key and history.
Try it yourself
Practise as Alex Morgan in the demo.
View as Alex Morgan. Open the Portal team. Which sprint is it in, and where would you go to move one of its stories?
Open the demo as Alex Morgan Password pulse-demo-2026. The demo resets every night.
The examples use a made-up healthcare organisation. DelPulse is not only for healthcare: it can be set up for any industry, with your own names for every portfolio, programme, product and team.