Hardcored "Operation" role in gitlab?

A link to the original comment: https://gitlab.com/gitlab-org/gitlab-ce/issues/12736#note_191120042

Our use case for a special "Operation" role:

We are small game company with about 40 people. Here we have both engineering and operation folks using Gitlab. Right now we are dealing engineering with existing permission models just fine. But for op people we want them to have full access to issues and wiki sections, but no access the source. Op people often file bug reports directly, while also maintain the documents in wiki. This special role is meant is to reduce complexity to non-tech people, thus keeping the experience simpler for them, and to reduce unnecessary code exposure and risk.

This is almost the only missing feature that prevents us from doing a full-scale to gitlab. I understand that gitlab is inherently a dev-oriented product, and the company very much inherits the open source value, but gitlab so far has shown so much potential to incorporate other roles into the product. A more flexible permission model(not necessarily super granular) seems very reasonable. Hopefully you guys could recognize the value of source protection and the need for non-tech people to use gitlab along with devs.

As for the specific feature. Ideally a "Operation" role with permission to access wiki and issues, but not code will be ideal. Thanks.