...
- Navigate to the Jira Administration Settings > Issues > Custom fields
- Click on the Add custom field button
Create the following required custom fields:
Field Type Field Name Renderer Advanced: Text Field (read only) VERA Sync ID Default Text Renderer Advanced: Text Field (read only) Pending Tasks Default Text Renderer Create the following optional custom fields as needed:
Field Type Field Name Renderer Advanced: Text Field (single line) Revision Default Text Renderer Advanced: Text Field (read only) Revision Number Default Text Renderer Advanced: Text Field (read only) Signatures Wiki Style Renderer Note title Signatures Field The VERA integration with Jira utilizes Jira Read-Only custom fields. VERA will attempt to write the entire approval route to the Jira Signatures field if the field is present in the Jira project. If the approval route contains over 255 characters the Approval will fail since VERA is attempting to write over 255 characters to the field. The Signatures field should be removed as a workaround.
- Follow the directions starting at step #4 in the below section to complete the custom field setup for the first VERA enabled Jira project
...
| Info |
|---|
If you have multiple Field Configurations that need the Signatures field, repeat this process to add them to each needed Field Configuration. |
| Note |
| The VERA integration with Jira utilizes Jira Read-Only custom fields. VERA will attempt to write the entire approval route to the Jira Signatures field if the field is present in the Jira project. If the approval route contains over 255 characters the Approval will fail since VERA is attempting to write over 255 characters to the field. The Signatures field should be removed as a workaround . |