We left Jira too.
Procyon exists because RoushTech ran Jira for years and finally stopped. This page is the story of why, and what we built instead. If your team is having the same argument right now, you are in the right place.
The short version
Why we stopped.
We ran our own projects and our client work on Jira for years. The grievance folder filled slowly: pages you could watch load, a version field that pretended to be release management, and a marketplace purchase standing between us and things a tracker should already do.
Then Atlassian killed Server. The self-hosted product we had built our workflow on was retired out from under us, and Data Center pricing is not aimed at teams our size. The message was hard to miss: move into their cloud on their terms, or leave.
So we left. We built Procyon, moved every project over with the importer we now ship, and have run RoushTech on it every day since.
What we changed
The parts we rebuilt on purpose.
Releases are the point
In Jira, a version is a label on tickets. In Procyon, versions carry their own progress, freeze dates, and slip history, and the release radar shows what is actually shipping.
Responsibility, not archaeology
Every status names the role responsible, so a stalled ticket answers "who is this waiting on" without a dig through the comment thread.
Support desk included
Jira sells the service desk as a second product. Procyon's customer portals, SLAs, canned responses, and CSAT surveys are part of the tracker.
Time tracking included
Work logs live on the ticket, with permissions for who can log time and who can correct it. No add-on subscription between you and your own hours.
No app store
If a tracker needs a marketplace to be complete, it is not complete. Procyon does not have one, on purpose, and never will.
Your own instance, always
Atlassian retired Server. Procyon starts from it: an instance that is yours alone, in our cloud or on your hardware, same product either way.
The honest part
What Jira still has on us.
Jira has agile boards and sprints; Procyon does not yet. Jira has a marketplace of thousands of add-ons; we think that is how a tracker ends up unfinished, but if your workflow depends on ten of them, plan accordingly. And Jira is mature software while Procyon is pre-release: we run our company on it every day, and we are not ready for you to run yours on it yet.
When you are ready, your history comes with you. The importer brings tickets, comments, attachments, versions, and links, with live progress while it runs. Leaving Jira should not cost you your past.
Procyon is being built, and written up as it ships.
The blog covers what ships and why. Subscribe to the RSS feed or check back as releases land.