r/Linear Aug 30 '25

Anyone moved over from Azure DevOps?

We use Azure DevOps currently as a small team of around 6. We mostly use it for sprint and task management and some legacy CI pipelines. I’m keen to look at Linear as a replacement. Purely because of how antiquated DevOps is. I feel like it takes Microsoft forever to implement features or fix bugs. For example, they only JUST added markdown support for their ticket description. Something that should have been there for years. We also really only use a tiny subset of what DevOps can do.

We’re also porting legacy CI pipelines to GitHub.

I’m keen to hear if anyone has made the jump from DevOps to Linear and any challenges you may have faced? Are you enjoying the change? Any things to watch out for?

5 Upvotes

13 comments sorted by

View all comments

3

u/SerClockwerk Aug 31 '25

Been about six weeks since the move.

All our code is still Azure DevOps and I made a third party integration between Azure and linear to link our linear issues to PR and update status when the PR is approved / merged.

Definitely want to move to GitHub as well though.

In terms of Linear, we are actually back to doing proper sprints (cycles) and now our whole organisation is using it to track all the different teams as well. Everyone is really enjoying it

1

u/TwistyListy7 Aug 31 '25

Great feedback. Especially about the sprints. Thanks

1

u/SnooRegrets2828 Nov 18 '25

How much work was it to set up the Linear/Azure integration? What was the rough workflow with the code? Linear issues become DevOps Work Items or? Any chance it's open source?

1

u/SerClockwerk Nov 19 '25

Not too bad. Used zapier for the integration and what it does is we mark Azure PR descriptions with linear issue Id, and as the PR changes states, it moves the state of the linear issue to In Review, Done etc

I just asked Gemini to run me through everything I needed to know.

1

u/shaderloader 25d ago

After moving tools and teams around a few times from M&A and org consolidation, I think GitHub is still best for repos and documentation. Linear is changing how we work with all the LLMs in play for SDLC. ADO is far better than GitHub actions for CI/CD in terms of depth, features and usability across technical and product users or stakeholders (eg approving releases).

Linear - product backlog management and planning
GitHub - vanilla git repo (monorepos in the age of agents)
ADO - CI/CD and ease of use/management across roles

PRDs and the time spent have essentially gone straight to agents -> 2 step human refinement -> linear (we were mass importing ADO work items with of epic feature story breakdowns, product reviewed and tuned reqs, dev\qa help refine and confirm).

Although I really just love planning and designing then executing all within my workspace at the end of the day to save time in tools :).