/
Jira Software Functions
Jira Software Functions
Please note that some of the epic operations do not work on next-gen projects.
The cloud version uses the following structures:
JSprint
int id; //sprint id
string name; //sprint name
date startDate; //start date, may be null
date endDate; // end date, may be null
date completeDate; // non-null only for completed sprints
string goal; //goal of the sprint
state state; //active, future, completed
int boardId; // the board id it belongs to
JBoard
int id; // the id of the board
string name; //name
string type; //kanban, scrum, simple
JEpic
int id; // id of the epic
string name; // name of the epic
string summary; // summary
boolean done; // true if this is a done epic
Example 1
The following plans a sprint directly from the backlog issues which have the Story Points field set.
Example 2
Installing the following listener on the Sprint Created event will allow you to create automatically recurrent issues:
Peacock
Related content
issueInEpic
issueInEpic
Read with this
Agile sprints
Agile sprints
More like this
Predefined Structure Types
Predefined Structure Types
Read with this
Plan Mode
Plan Mode
More like this
getUserByFullName
getUserByFullName
Read with this
Plan Mode
Plan Mode
More like this