JJUPIN Software enriches the SIL language by allowing users to directly access the custom fields created by JIRA Software, just like any other JIRA custom fields.
Supported custom fields are:
| Custom Field | Read/Write | SIL Type | Value | Notes |
|---|---|---|---|---|
| Sprint | Read/Write | number [] | List of sprint IDs | Issues assigned to multiple open/started sprints will show up only one in the Rapid Board. It is recommended that you should not assign an issue to multiple open/started sprints. |
| Rank | Read-only | number | The rank | To set the rank, use the JIRA Software Supported Fields |
| Epic Status | Read/Write | string | A valid option for the Epic Status. (by default, one of: To Do, In Progress, Done) | Requires the issue to be an Epic. |
| Epic Link | Read/Write | string | The issue key of the epic this issue belongs to. | If set to an empty value, will remove the issue from the epic. |
| Epic Name | Read/Write | string | The name of the epic | Requires the issue to be an Epic. |
| Epic Colour | Read/Write | string | Color code of the epic links that are shown on the child issues. | Requires the issue to be an Epic. Accepts any valid CSS value for background-color. (e.g. #EAEBDD, rgb(127, 67, 233), #cab, yellow) |
| Story Points | Read/Write | number | The number of story points on the issue. | |
| Flagged | Read/Write | string [] | A valid option for the Flagged field. | |
| Business Value | Read/Write | number | The business value of the issue. |
Back to basics
Since most of these custom fields contain a blank space in their name, don't forget to use #{ and } if you'd like to use the name instead of id/alias.
Examples
#{Story Points} = 8;
#{TEST-1.Epic Name} = "Best Epic name ever";
print(Rank);
print(TEST-1.Sprint);
print(#{TEST-1.Sprint});
print(#{TEST-1.Business Value});