Name must start with a expected version tag ex: v1.4.6
. An optional small description is allowed ex: v1.4.6 Custom Title
the only these characters are allowed in the title [A-Za-z\d\s\-\:]
- tagged version is not deployed to customer
- pre-release may be available
- available in
Pre Release
for further testing - not deployed to customers
- deployed (or will deploy) to customers
- marked as a
Latest Release
The issue title should be as short as possible at describing the 10k foot view and contain only these characters [A-Za-z\d\s\-\:]
.
- need programming
- being programmed
- having discussions on
- have been programmed
- passed locally testing and CI testing
- w/ label duplicate, merged, invalid, wont fix, etc.
- Do not reopen issues if its just a question
- a notification still gets sent to the subcribers, even when closed
- Reopen the closed issue if bug is proven to persist
- evidence must be provided, not just a message "Not working"
- Create new issue (referenced to closed issue) is a new related issue is found
- but is significant enough that it deserves its own Issue
- reference at top of issue via this markdown
> new issues related to #54
wip
a programmer is actively working on this issueneeds testing
(typically on closed issues) this is needing further testing before deploymentfeature
when there new concepts presented- required a detailed list of objectives (using
- [ ]
markdown) describing what is needed to be done in the feature
- required a detailed list of objectives (using
enhancement
when an existing feature needs enhancement- never
feature
andenhancement
- never
question
when the issue is more of a missunderstanding or a questionbug
when a feature is found to have a bug- required provide step-by-step methods to reproduce. (no one liners here)
wontfix
- when closed: no code should be commited
duplicate
another issue exists already with the presented concept or merged into another ticket- optional providing referenced ticket