Redmine Issue Fields
This page outlines the fields used in the VisIt team's issue tracking system. In addition to standard redmine fields we added some a custom fields to capture info to identify the scope of an issue and prioritize work. VisIt users submitting issues should try to enter as much info as possible and then rely on defaults if necessary. When submitting a bug report a detailed description of how to reproduce the issue is very helpful. VisIt developers will adjust fields related to prioritization as issues are reviewed and investigated.
 Issue Fields common to both the Bug & Feature Trackers
|Status||Identifies the current state of an issue. See Issue Lifecycle for details of issue states.|
|Priority||A general classification of how important it is to resolve an issue.|
|Assigned to||The developer (if any) that is currently assigned to investigate or resolve an issue.|
|Target Version||The release (if any) that the team currently planning to resolve an issue for.|
|Estimated Time||An estimate of the number of hours required to resolve an issue.|
|OS||The operating system an issue is related to.
'All' is used for bugs & features that are OS agnostic.
|Support Group||The funding group this issue is associated with.
'Any' is used if a support group cannot be identified.
 Additional Bug Tracker Fields
|Likelihood||An estimate of how often a bug occurs.|
|Severity||An estimate of how severe a bug is when it occurs.|
|Found in Version:||Which version of VisIt a bug was discovered in.|
 Additional Feature Tracker Fields
|Expected use||An estimate of how often a feature be used if implemented.|
|Impact||An estimate of how useful a feature will be to users & developers if implemented.|
Finally, there is this helpful Redmine Email Cheatsheet that describes generally how to submit issue events via email.