Hi! I'm one of the product managers at GitLab that will be contributing to the development of requirements management. I don't believe we've decided that it will only be an Ultimate level feature. The label was added to the epic (https://gitlab.com/groups/gitlab-org/-/epics/707) before any conversation had taken place...or even before there were concrete requirements to build requirements management ;)
We do our best to align features with the likely buyer according to our pricing model (https://about.gitlab.com/handbook/ceo/pricing/). Sometimes we don't get it right and need to fix our mistake after a feature is launched based on feedback from our wider community (example: https://gitlab.com/gitlab-org/gitlab-ee/issues/13856). We have been and will always be transparent about our pricing model and our mistakes in aligning new features with it.
If you're interested in collaborating with us as we build out requirements management, we would love that. It will help us build the right features for the right likely buyer. Please leave some additional thoughts on the epic discussion if you have them!
Oh, I don’t doubt that the feature would make most sense in the Enterprise tier, but we’re on Atlassian right now, whose price is often equated to free compared to Gitlab.
Convincing them to spend $20/developer/month is going to be hard. Convincing them to spend $100/dev/month is going to be a whole different ballgame (even if it’s ultimately perfectly great unit economics if gitlab increases productivity by at least 2%).
Thought the same. Let’s try to pick HN’s brain: is there an alternative that you guys use predominantly, that can “talk” with gitlab’s or github’s issues?
Not cool, it’s only in Ultimate. No way am I going to be able to get my company to shell out for that.