Why SIL ?
If you need to customize JIRA really deep, choose SIL through our one-of-the-kind plugins JJUPIN and / or Blitz Actions. The top reasons to use it are:
- really delivers fast.
- shields you form the JIRA internals,
- consistent from version to version
- extensible (routines and custom fields)
- covers many other commercial plugins functionalities.
Choosing SIL is a smart thing to do:
- If you really care about standard programming practices, you can move workflows from test to production environments very quick.
- Scripts can be easily adapted and modified on the fly
- You pay only once, then you can cover countless customizations, which otherwise would require a dozen of plugins
- It is supported and YOU have the power.
In our opinion (biased, of course) it is the best option you could have for JIRA customization.
An Example
First of all, here is a short example so you know what to expect:
string k; assignee = "admin"; reporter = assignee; created = currentDate(); description = "some description"; dueDate = currentDate() + "1d"; env = "environment"; estimate = "2d" + "3h"; originalEstimate = "1d 4h" + "21h"; priority = "Critical"; if(not contains(summary, "test")){ summary = "test " + summary; } else { summary = "random summary assigned"; } spent = "2d"; updated = currentDate() - "1d"; votes = votes + 1; workflow = "TWFLScheme"; if(issueType == "Bug"){ issueType = "Task"; } else { issueType = "Bug"; } project = "TSTP"; //Custom fields here UPPG = "admin"; //time interval custom field if(isNull(tt1)) { tt1 = estimate + "1h"; } else { tt1 = tt1 + "1h"; } //number custom field if(isNull(cfnumber)){ cfnumber = 1; } else { cfnumber = cfnumber + 1; } //create routine k = createIssue("TSTP", "", issueType, "auto-created issue"); %k%.votes = %k%.votes + 1; //autotransition autotransition(721,key); //or: //autotransition("Send report","PRJ-123");
Do not worry if all is not clear from the start, it will all make sense after you finish reading this guide.