diff options
| author | Brian Coca <brian.coca+git@gmail.com> | 2016-07-01 10:30:12 -0400 |
|---|---|---|
| committer | Brian Coca <brian.coca+git@gmail.com> | 2016-07-01 10:31:11 -0400 |
| commit | 07f39d92a0a9841b339b1e1fb509e5152b5d3417 (patch) | |
| tree | c134b14b59863b6f837f9434ebd6ac175cc954e8 /ticket_stubs | |
| parent | faec03aabcdcd905eb2d4b45a9b92432f78ea670 (diff) | |
| download | ansible-07f39d92a0a9841b339b1e1fb509e5152b5d3417.tar.gz | |
updated needs_template to reflect github feature
Diffstat (limited to 'ticket_stubs')
| -rw-r--r-- | ticket_stubs/needs_template.md | 18 |
1 files changed, 7 insertions, 11 deletions
diff --git a/ticket_stubs/needs_template.md b/ticket_stubs/needs_template.md index 894532b5e7..05bb9672d1 100644 --- a/ticket_stubs/needs_template.md +++ b/ticket_stubs/needs_template.md @@ -1,13 +1,13 @@ Can You Help Us Out? ==================== -Thanks for filing a ticket! I am the friendly GitHub Ansibot. +Thanks for filing a ticket! It looks like you might not have filled out the issue description based on our standard issue template. You might not have known about that, and that's ok too, we'll tell you how to do it. We have a standard template because Ansible is a really busy project and it helps to have some standard information in each ticket, and GitHub doesn't yet provide a standard facility to do this like some other bug trackers. We hope you understand as this is really valuable to us!. -Solving this is simple: please copy the contents of this [template](https://raw.githubusercontent.com/ansible/ansible/devel/ISSUE_TEMPLATE.md) and **paste it into the description** of your ticket. That's it! +Solving this is simple: please use the issue template provided when you open a new issue. That's it! If You Had A Question To Ask Instead ==================================== @@ -16,15 +16,6 @@ If you happened to have a "how do I do this in Ansible" type of question, that's However, if you think you have a bug, the report is the way to go! We definitely want all the bugs filed :) Just trying to help! -About Priority Tags -=================== - -Since you're here, we'll also share some useful information at this time. - -In general tickets will be assigned a priority between P1 (highest) and P5, and then worked in priority order. We may also have some follow up questions along the way, so keeping up with follow up comments via GitHub notifications is a good idea. - -Due to large interest in Ansible, humans may not comment on your ticket immediately. - Mailing Lists ============= @@ -34,3 +25,8 @@ If you have concerns or questions, you're welcome to stop by the ansible-project * https://groups.google.com/forum/#!forum/ansible-devel - for discussion on how to implement a code change, or feature brainstorming among developers Thanks again for the interest in Ansible! + +Closing this ticket +=================== + +If you still feel like this should be a ticket, please reopen a new one and properly fill in the template. |