NeoAnd/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2025-07-17 12:42:52 -06:00
Code Issues Actions 7 Packages Projects Releases Wiki Activity

Updated Issue Intake Policy (markdown)

Jeremy Stretch 2021-09-09 09:30:05 -04:00
parent 8e85dd94eb
commit 03ab1b55b0
1 changed files with 10 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
Issue-Intake-Policy.md

@ -52,12 +52,14 @@ This page serves to define the official policy for opening and processing GitHub
[[images/netbox_triage_bug.png]] [[images/netbox_triage_bug.png]]
1. Verify that the reported behavior is unexpected. 1. Evaluate whether sufficient detail has been provided to reproduce the described behavior.
1. If not, apply the `INSUFFICIENT DETAIL` canned response and apply the `status: revisions needed` label.
2. Verify that the reported behavior is unexpected.
1. If the reported behavior is considered normal, apply the `EXPECTED_BEHAVIOR` canned response and apply the `status: revisions needed` label. 1. If the reported behavior is considered normal, apply the `EXPECTED_BEHAVIOR` canned response and apply the `status: revisions needed` label.
2. Attempt to replicate the reported bug on the current NetBox release (i.e. the `master` branch) by performing the steps detailed in the issue. 3. Attempt to replicate the reported bug on the current NetBox release (i.e. the `master` branch) by performing the steps detailed in the issue.
1. If you are unable to reproduce the reported error or behavior, apply the `UNABLE_TO_REPRODUCE` canned response, and optionally ask for further clarification on how they encountered the reported issue. Also apply the `status: revisions needed` label. 1. If you are unable to reproduce the reported error or behavior, apply the `UNABLE_TO_REPRODUCE` canned response, and optionally ask for further clarification on how they encountered the reported issue. Also apply the `status: revisions needed` label.
3. Assuming you are able to successfully replicate the reported issue, apply the `type: bug` and `status: accepted` labels. 4. Assuming you are able to successfully replicate the reported issue, apply the `type: bug` and `status: accepted` labels.
4. If there are external factors preventing you from testing the reported issue (such as another bug interfering with testing), apply the `status: blocked` label and leave a comment explaining why. 5. If there are external factors preventing you from testing the reported issue (such as another bug interfering with testing), apply the `status: blocked` label and leave a comment explaining why.
# Canned Responses # Canned Responses
@ -83,6 +85,10 @@ Below is a library of standard responses that can be used to save time when addr
`Thank you for submitting your idea. Unfortunately, the proposed feature falls outside the scope of functionality that NetBox aims to provide. As NetBox is an open source application with limited development resources and a persistent backlog of existing work, it is crucial that we limit the scope of development to ensure it remains a maintainable project for many years to come. Thank you for your understanding.` `Thank you for submitting your idea. Unfortunately, the proposed feature falls outside the scope of functionality that NetBox aims to provide. As NetBox is an open source application with limited development resources and a persistent backlog of existing work, it is crucial that we limit the scope of development to ensure it remains a maintainable project for many years to come. Thank you for your understanding.`
### INSUFFICIENT_DETAIL
`Thank you for opening a bug report. Unfortunately, the information you have provided is not sufficient for someone else to attempt to reproduce the reported behavior. Remember, each bug report must include detailed steps that someone else can follow on a clean, empty NetBox installation to reproduce the exact problem you're experiencing. These instructions should include the creation of any involved objects, any configuration changes, and complete accounting of the actions being taken. Also be sure that your report does not reference data on the public NetBox demo, as that is subject to change at any time by an outside party and cannot be relied upon for bug reports.`
### PLUGIN_CANDIDATE ### PLUGIN_CANDIDATE
`Thank you for submitting your idea. Although the proposed functionality falls outside the current scope of NetBox's core feature set, it may make a good candidate for a [NetBox plugin](https://netbox.readthedocs.io/en/stable/plugins/), and we encourage you to pursue its development and a standalone project. Please reach out [via our mailing list or Slack channel](https://github.com/netbox-community/netbox/wiki) if you need any assistance.` `Thank you for submitting your idea. Although the proposed functionality falls outside the current scope of NetBox's core feature set, it may make a good candidate for a [NetBox plugin](https://netbox.readthedocs.io/en/stable/plugins/), and we encourage you to pursue its development and a standalone project. Please reach out [via our mailing list or Slack channel](https://github.com/netbox-community/netbox/wiki) if you need any assistance.`