...
- The Affects Version/s field indicates the version where the issues was observed or can be reproduced.
- This is N/A for new epics, features, and user stories.
- For bug fixes, select only a released version. For example, do not write a bug against 2.10.0 if it has not been released yet.
- For bug fixes, only select a version if the bug actually manifests itself in that version; do not write a bug against 2.9.0 if the bug is not in 2.9.0.
Fix Version/s Field
...
The Fix Version/s
...
field indicates the version in which the issue is resolved. For planning purposes, this field can indicate the version this issue is intended to be resolved by.
- This field is required when an issue is resolved.
- This field should not be populated for changes that can be observed in DIB versions. For example, spikes generally should not not have the Fix Version/s field populated.
- If ticket has been completed on both the bug fix branch and the master branch, the Fix Version/s field should include both versions (e.g.
).Jira Legacy server System JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 604952f1-6481-38bd-ad7b-d576f67ec488 key DDF-3363
Description Field
The description field is a detailed, narrative description of the issue. General guidelines for the description field:
...