Skip to content

Conversation

zarend
Copy link
Contributor

@zarend zarend commented Jun 24, 2022

Remove the Troubleshooting issue template. Add contact links to
StackOverflow, Gitter and Google Groups.

The support request Saved
Reply

summarizes well why issues are not the best place to help support help.

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular.

If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.

@zarend zarend added docs This issue is related to documentation merge safe target: patch This PR is targeted for the next patch release labels Jun 24, 2022
@andrewseguin
Copy link
Contributor

andrewseguin commented Jun 24, 2022

I was suggesting that we just change the wording here to further discourage users from opening a troubleshooting issue

image

E.g. "Issues should not be opened for troubleshooting."

And the template itself can be a bit more blunt about not wanting these issues opened, rather than providing inputs that continue to guide the user to giving information.

@jelbourn
Copy link
Member

You can add entries here that just link somewhere else- maybe that's the best thing?
e.g. https://github.com/angular/angular/blob/main/.github/ISSUE_TEMPLATE/config.yml#L12-L14

@zarend zarend self-assigned this Nov 28, 2022
Copy link
Contributor

@mmalerba mmalerba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@mmalerba mmalerba added the action: merge The PR is ready for merge by the caretaker label Nov 28, 2022
Remove the Troubleshooting issue template. Add contact links to
StackOverflow, Gitter and Google Groups.

The support request [Saved
Reply](https://github.com/angular/angular/blob/main/docs/SAVED_REPLIES.md)
summarizes well why issues are not the best place to help support help.

>>>
Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on [StackOverflow](https://stackoverflow.com/) using tag `angular`.

If you are wondering why we don't resolve support issues via the issue tracker, please [check out this explanation](https://github.com/angular/angular/blob/main/CONTRIBUTING.md#question).
@angular-robot angular-robot bot added the area: docs Related to the documentation label Feb 11, 2023
@angular-robot angular-robot bot merged commit 7ba9fa7 into angular:main Feb 15, 2023
angular-robot bot pushed a commit that referenced this pull request Feb 15, 2023
Remove the Troubleshooting issue template. Add contact links to
StackOverflow, Gitter and Google Groups.

The support request [Saved
Reply](https://github.com/angular/angular/blob/main/docs/SAVED_REPLIES.md)
summarizes well why issues are not the best place to help support help.

>>>
Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on [StackOverflow](https://stackoverflow.com/) using tag `angular`.

If you are wondering why we don't resolve support issues via the issue tracker, please [check out this explanation](https://github.com/angular/angular/blob/main/CONTRIBUTING.md#question).

(cherry picked from commit 7ba9fa7)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Mar 18, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker area: docs Related to the documentation docs This issue is related to documentation target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants