Man, PT was so good. Linear is okay, but I find it really slow - more than once I've opened an existing issue and started editing it, only for a few seconds later the actual content to pop in and make a mess.

My biggest issue with Linear is that it doesn't think about cycles the way Pivotal did sprints. Or more accurately, it's in what PT called "commit mode" all the time.

If your cycle ends with a bunch of work undone, it rolls into the next cycle. If that cycle already a full capacity of work planned, well, now your cycle is at 150% or whatever. Repeat. The solution, presumably, is to stop creating new cycles.

But what PT would do, and seamlessly at that, is rebalance the sprints. Your project manager wants to move a number of stories to the top of the backlog? Great, but now that item projected for three sprints out is now four sprints out. The velocity and the projections were extracted from reality, not mandated from on high.

I asked Linear if they could add this -- a cycle rebalance. I was told, no, this simply isn't something they want to do, but maybe I could do it with zapier. Trying to get them to understand why I wanted this was like trying to explain air to a fish. It simply did not compute.