| Button handy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
The purpose of this document is to describe general best practices to follow while scripting.
...
Develop as much as possible from the SIL Manager. Developing from the SIL Manger tends to give the user a better sense of what the code does and is much faster.
Start with one routine function as a proof of concept.
Add loops and if statements after.
Hardcode at first to get a result.
Refactor hardcoded values with with variables.
If possible, test Live Fields in the edit screen before trying in Jira Service Desk portal or create screen. The JSD portal tends to be more complicated and more can go wrong.
...
Often other users have already done something similar to what you would like to do. Find an example on the Atlassian Community?
Look for routinesfunctions.
First look for routines functions in the Jira Integration RoutinesFunctions section of the documentation. Most routines functions dealing with Jira will be found here.
The second place to look is the Jira Administration RoutinesFunctions.
The last category of routines functions has to deal with things like math, string manipulation or array routinesfunctions.
If the routine function you are looking for does not exist, consider implementing a script which consumes an Atlassian REST API (Jira Server/DC), (Cloud).
When developing SIL scripts which consume REST API, try using getting results with httpGet().
| Info |
|---|
You are highly encouraged to use a SIL routine function if at all possible. Atlassian Java methods (and to a lesser extent, REST API) change all the time and can break your code. When using SIL, we take care of deprecated Java methods for you, so if you use SIL routinesfunctions, you will not need to update your code. |
...
| Page Properties | ||
|---|---|---|
| ||
|