There is no excerpt because this is a protected post.
Read More
There is no excerpt because this is a protected post.
Read MoreSometimes we need to create new tickets in Jira programmatically each first of month… (yes, in other words, we will create a recurring task each month) and a scheduled process stored in Jira is called “Service”. With Adaptavist Scriptrunner or MyGroovy plugins for Jira Server and a little groovy script we can create programmatically complex…
Read MoreThis “Groovy” trick for Jira allows us to create Jira issues automatically and repeatedly on demand! For the example, we will edit a Workflow and we will add a new Transition of type Recursive ( from All to Itself). And we name the Transition as “Clone issue and Linked Issues“. (NOTE: Remember after this to…
Read MoreIn this example we want to create a simple Listener for Jira to reopen issues when are closed/done and someone comments the ticket. Imagine, we have a ticket in status “DONE” And there is a “new comment”. Then, the Listener must reopen the issue, and the ticket becomes in “TO DO” status. In this example,…
Read MoreSometimes we need to raise new subtasks when other subtasks are finished. In this example we explain how we can do this in Jira using the famous plugin Adaptavist Scriptruner. The trigger of the action is the “transition”: when someone moves a subtask from one status to another. In this case, from “IN PROGRESS” to…
Read MoreLinkedin message of Nikita Teplov: … Hello everybody! We create an alternative to Script-runner, and we added a number of features which we had not had earlier. Features: – Scripts Registry for workflows (you can add inline scripts in the workflow) – Recurring tasks – Liseners – Scripted fields – Console for debugging – Scripts…
Read More