Your Jira alternative is currently a better replacement for a limited but important part of Jira features: clearly only an initial, promising feature set that will be expanded and improved. But in what direction?
The more technical side of software development (e.g. configuration, building and deployment of the releases)? Generic ticket handling and time tracking/accounting to expand the product's usefulness beyond specialized software product development teams? Integration with other software and processes?
The key for our platform will always be simplicity. For now, the plan is to head into the technical side of software dev (Gitlab, Bitbucket and integrations with CI/CD tooling), without alienating business teams.
One of the biggest issues with existing PM software is that it's purpose built for singular teams, vs providing utility to cross-functional teams (e.g. engineering and growth). And it's usually overly complex with significant configuration required.
We're seeing early signs of this with requests from teams/orgs to add in marketing, growth and design teams as they need to be in the loop of releases and the overall SDLC.
