Create an ISSUE MANAGER Licensing Tier for Ultimate
Ultimate Customer: https://gitlab.my.salesforce.com/0016100001ABpAc would like this feature.
Problem to solve
This is a problem with current GitLab Ultimate licensing structure. Guest users contribute to issues, Developers and above submit code. There is a need for an in between level (cheaper than devs) for people who manage issues but do not need all developer and CI/CD features. Current license model may prevent us from getting everyone fully using GitLab (due to cost for those who need to manage issues). There are some workarounds (like issue templates) but they aren't enough.
Proposed Solution
Request is to add an Issue Manager license level for Ultimate, paid but cheaper than full developer license.
Related Problem To Solve
Related issue is that we need a billing model that more accurately reflects actual usage. It is very easy to accidentally move someone from GUEST to FULL (e.g. a manager inadvertently sets someone to reporter in their group when the person is supposed to remain as GUEST). We can take responsibility for that, but if we make a mistake and have someone as a reporter for an hour or a day or 2 weeks, we don't want to pay $1200 for a mistake. I assume GitLab's intent is to have customers add more people to paid licenses.
Proposed Solution
Making billing something that reflects actual number of licenses and is based on # days of access/usage would enable it to be more realtime, and thus not something we need to worry about screwing up. Less worry means more likely to add people more often and an easier, more collaborative relationship. Another tactical solution would be that anytime a user is added with anything more than a Guest license, warn the person that they are about to spend $1200. (Of course that would be terribly annoying, so please don't actually implement that solution... but it is a risk of having distributed role management with no central controls.) I guess another solution would be to have a master list of all accounts and a maximum role level to prevent someone from inadvertently going into a paid license when they shouldn't. But that solution has problems too.
Implications
Intent of both of these is to use GitLab effectively within our organization and pay for the users and user levels we consume. Because the structure does not match our need it will result in...
- Using other tools instead of GitLab because GitLab is too expensive to use for issue management.
- Us overpaying for licensing and getting frustrated that it is too expensive for what we need (or for some roles) and thus deterioration of value and satisfaction.
- Having to pay $1,200 for an accidental incorrect role assignment is unreasonable, especially if it is fixed quickly. There should be a way to be charged for the number of consuming users, accurate to actual usage. Put the power in our hands to manage our costs and we will be happier with the product.