When uploading to Jira, CaseComplete automatically uploads the Name, Description, and Type fields to the corresponding Jira issue. (The type mapping is based on your selection in the Jira upload wizard).
For other fields defined in CaseComplete (both custom and built-in), the uploader creates Jira labels (aka tags). A label will only be created if the field uses a "choice list", i.e. it has a drop-down list of possible selections, for example, a Requirement's Status field. It won’t create labels for fields that are free-form text since those aren’t well-suited for tags. Since labels in Jira are navigable, they provide an easy way to filter items. For example, clicking a Priority1 label shows all items that have priority 1.
In addition, the uploader looks at all the fields defined in Jira for the type of issue being uploaded to, and if there’s a custom field in CaseComplete with the same name then it automatically maps those fields and uploads values from CaseComplete to the corresponding Jira field. However, there are some field types that CaseComplete can’t handle, for example Jira fields of type "user". This name-based mapping is for CaseComplete's custom fields only - it won’t do this for built-in fields such as Priority, Complexity, etc.
Finally, there are two special cases:
- If Stories in Jira have a custom field named Acceptance Criteria, CaseComplete will use it (otherwise they get appended to the issue’s description).
- Since Issues in CaseComplete don’t have names, by default the issue's description is uploaded to the title field in Jira (Jira calls this the summary field). However, if you have a custom field defined for CaseComplete Issues named Summary, it will use that for the issue's title instead, and put the text of the issue in Jira's description field.