...
- The feature or bug is classified as a known issue, i.e. as an inconvenience with a valid workaround available, and will by purpose not be changed.
- Being a known issue is an end status for a feature, therefore no further action will be taken.
- The issue is assigned one of the resolutions
- the feature works as designed (resolution:
works as designed
). - the issue not being fixed (resolution:
won't fix
). - the issue is caused by misapprehension of the underlying functionality (
bogus
)
- the feature works as designed (resolution:
Status | ||||||
---|---|---|---|---|---|---|
|
- The feature or bug is dismissed, e.g. due to architectural constraints or invalid requirements. The feature is not considered for future development.
- Being dismissed is an end status for a feature, therefore no further action will be taken.
- The issue is assigned one of the resolutions:
- the feature works as designed (resolution:
works as designed
). - the issue is caused by misconfiguration or misapprehension of the underlying functionality (resolution:
bogus
). - the issue not being fixed (resolution:
won't fix
). - the issue duplicating an issue and being resolved with that issue (resolution:
duplicate
) - the feature requirements being incomplete (resolution:
incomplete
). - the bug cannot be reproduced (resolution:
cannot reproduce
).
- the feature works as designed (resolution:
...