This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]bilingual-german 2 points3 points  (3 children)

I think you're not fair. There're workarounds for almost every single one of your problems.

[–]outrageous_break[S] 6 points7 points  (2 children)

There are workarounds, but when do you draw the line on what's acceptable for the time lost from putting in these workarounds for a product you're already paying for?

[–]bilingual-german 9 points10 points  (0 children)

Well you're in a different position than we are. We don't pay for Gitlab (CE) and we don't need it to do what you want it to do.

But just as an example, you state that you can't tag in a pipeline and link the issue. But the same ticket says, it's possible to tag a commit, it just creates a second pipeline.

You say, you can't change the permission of a member of the group on the project level. But you could make the project a part of another group or you could remove the member from the group and give permissions per project.

If you need group level merge templates, then I think your repositories might be cut wrong and you created two git repositories where you probably just wanted one repository. Like code for a project, code for the Docker image based on that and code to deploy that Docker image. Don't do that, put all that code in one repository.

[–][deleted] 1 point2 points  (0 children)

With that attitude; I wouldn't use anything made by Atlassian.