Update process for issue tracker
What does this MR do?
- Remove old policy regarding closing inactive MR/issues since it's not valid anymore.
- Update policy about closing issues only
- Link to support page
Why was this MR needed?
We get 1-3 issues per day on the issue tracker and most of the are question on how to use GitLab Runner or a feature not working because of some misconfiguration. This litters the issue tracker quite a bit and takes resources from engineers doing support where they should be working on deliverables.
Edited by 🤖 GitLab Bot 🤖