DevOps stages team division is confusing
**I am sure that there is an issue about this somewhere but I was unable to find it. If there is one, please let me know and I will close this one in favor of the existing issue. **
Problem description
With the engineering team split to devops stages it is very time consuming finding out which team owns what part of the application. In some cases, I personally just give up and do not assign a team or in most cases I don't want to bother creating an issue.
In the above linked issue, I went to product categories and searched for Repository mirroring
(and all permutations of it). Since I failed to find it, I then searched for project settings
and project management
. I found things under project management
but that was related to issue boards. After that, I read through the whole page to find any hint of where to look next and I had found none.
I did find this which sank my hopes that I'll be able to find the answer after which I gave up on labeling properly.
This is just one example of many many others encountered daily.
Problem solving proposal
I am losing hope that a handbook will be a good place to resolve this, it's going to just get more difficult as we add more items to the product.
Is it possible to add this to GitLab itself? Without looking into technical feasibility, would it be possible to add team ownership per page, maybe as part of the performance bar
?
That would allow anyone, not only GitLab Inc. to see which team an issue needs to be reported to.
At this point, I'd take any improvement over the handbook solution, so I am open for any ideas.