+ *
+ * project |
+ * yes |
+ * yes |
+ * String |
+ * The key of the Jira project in which to create the issue(s). Usually 3-4 characters such as PRJ. |
+ *
+ *
+ * type |
+ * yes |
+ * yes |
+ * String |
+ * The type of the issue(s) to create. |
+ *
+ *
+ * epic |
+ * no |
+ * yes |
+ * String |
+ * The issue key (PRJ-123) of the epic to add the issue(s) to. |
+ *
+ *
+ * securityLevel |
+ * no |
+ * yes |
+ * String |
+ * The security level to set on the issue(s). |
+ *
+ *
+ * summary |
+ * yes |
+ * no |
+ * String |
+ * A short, single-line summary of the issue. |
+ *
+ *
+ * description |
+ * no |
+ * no |
+ * Text |
+ * A complete description of the issue. May contain Jira markup formatted text and be many lines of text. The YAML indenting, of course, will be
+ * removed. |
+ *
+ *
+ * assignee |
+ * no |
+ * yes |
+ * String |
+ * The username of the person to assign the issue(s) to. |
+ *
+ *
+ * components |
+ * no |
+ * yes |
+ * Set<String> |
+ * A set of names of the project components to add to this issue. If both the issue & configuration have components, the union of the sets will be
+ * applied to the issue. Remember components are per-project, if you are creating issues across multiple projects. |
+ *
+ *
+ * labels |
+ * no |
+ * yes |
+ * Set<String> |
+ * A set of labels to apply to the issue(s). If both the issue & configuration have labels, the union of the sets will be applied to the
+ * issue. |
+ *
+ *
+ * relationships |
+ * no |
+ * yes |
+ * Map<String, Set<String>> |
+ * A map from jira links types to the issues to link to this one. Linked issues may be specified by key if they're already in Jira, or by summary
+ * if they are to be added by this file. |
+ *
+ *
+ *