Live data from Hacker News

Pivotal Tracker will shut down

pivotaltracker.com

161–170 of 271 posts

Re: Pivotal Tracker will shut down

#161
post #127
post #47

The thing that I always liked about Pivotal is that it was visibly obvious that there was only one queue. It forced everyone to ruthlessly prioritize and make the hard decisions. In this moment, do you want me working on this bug, or this new feature? You have to decide - you get one or the other. It avoided the "Everything is a high priority" dilemma.

That sounds more like a disastrous missing feature to me. A good productivity tool doesn’t dictate how teams work. I’d rather have a tool that’s more customizable.

> I’d rather have a tool that’s more customizable.

You think you would, until you do, and by then it's too late.

It's important to have good processes, but the point of all those processes is to help you make things more efficiently. Anything that leads to you spending extra time serving the process directly reduces the amount of real work you can do.

Re: Pivotal Tracker will shut down

#165

I could have called this years ago when I found out they exclusively use and enforce pair programming in-house https://tanzu.vmware.com/content/blog/what-s-the-best-way-to...

> I could have called this years ago when I found out they exclusively use and enforce pair programming in-house

No, you could not have.

The environment that birthed Pivotal Tracker had the same culture, and the death of PT is a consequence of multiple profitable acquisitions, eventually into a multinational semiconductor corp that has no use for a small SaaS devtools product.

You could probably have called it based on the acquisition chain though. Many of us have been hoping to be surprised. Our luck has run out.

Re: Pivotal Tracker will shut down

#166
post #52

Earlier quoted context omitted.

Linear is the one I've settled on, it stays out of my way. For now. Looking at the competition it's only a matter of time before it becomes bloated to justify valuations. https://linear.app/

As soon as the AI features start showing up in Linear, it's time to jump ship. You know for sure VCs are pushing for that in the weekly meeting.

it's been there for about a year. you can use plain text to search issues, and the slack bot will auto-create titles when you create issues from there.

Re: Pivotal Tracker will shut down

#168
post #114

Earlier quoted context omitted.

Both OVH and Hetzner offers unmetered connections for their dedicated servers, only had good experience with both so far (besides when one of OVH's data centers burned down, but hoping that was a exceptional situation)

Backup to Backblaze B2, or, depending on architecture, rely on their object storage for hot data (depending on data cache and tier requirements). They partner with Cloudflare for free egress (on the Backblaze side) of public content as well. https://www.backblaze.com/cloud-storage/pricing https://www.backblaze.com/blog/backblaze-and-cloudflare-part...

Cloudflare’s subscription agreement for self-serve accounts limits serving non-HTML content, including "video or a disproportionate percentage of pictures, audio files, or other non-HTML content."

Re: Pivotal Tracker will shut down

#169
post #9

Unfortunate. Of all the PM tools I've used, I hated Pivotal the least. It made it easy to do the things that were frequently done. It limited customization down to a sane level. And it generally seemed to stay out of the way (significant look at Jira).

We found https://www.shortcut.com less opinionated than Linear and a closer 1 for 1 to Pivotal. They're all getting a little bloated, wish one would dial it back vs keep adding (which feels like the inevitable future for Linear).

Re: Pivotal Tracker will shut down

#170
post #113

Earlier quoted context omitted.

I don't think you'd have to consider migration all the data from Pivotal, but lets assume 10% just in case? Lets say that's 100TB in total (on disk), which you could host with 10x storage boxes from Hetzner, 24 EUR each per month, so 240 EUR in total, which includes 10 unmetered connections (1 per box).

> I don't think you'd have to consider migration all the data from Pivotal... I do. You might not have demands to migrate all data from all of your potential customers, but far, far more people than you might expect treat their issue tracking system as a system of record and external memory for a HUGE assortment of things. One hugely (and obviously) useful query chain that such a system answers is "Hey, this customer…

Obviously I meant 10% of all customers would hypothetically migrate from Pivotal to this new imaginary service, not that 10% of the data from each customer would be migrated... So 100% of the data migrated from 10% of the Pivotal user base, pretty generous assumptions I think.
Post reply on HN