...
This post function can be used on the Create transition to set a different issue security level depending on whether the issue is being created by a developer or by any other user.
Transition parent issue
Info | ||
---|---|---|
| ||
This feature is available for the Jira server deployment option only. We plan to add it to the Cloud version in the near future. |
A SIL post function that triggers a named transition on the parent issue of the current sub-task:
...
When executing the transition on sub-task, the "Start Progress" transition will be triggered on the parent issue, if this transition is valid for the current status of the issue.
Sending a custom email
Info | ||
---|---|---|
| ||
This feature is available for the Jira server deployment option only. We plan to add it to the Cloud version in the near future. |
A SIL post function that sends a custom email. For example, the reporter of the issue wants to be notified when the assignee resolves the issue. You can do this with the following code:
...
Add a comment to all blocked issues when this issue is transitioned
...
Info | ||
---|---|---|
| ||
This feature is available for the Jira server deployment option only. We plan to add it to the Cloud version in the near future. |
Adding a comment on behalf of the current user, to all blocked issues by the current issue transitioned:
...
Automatically adding or removing watchers from a workflow transition
Info | ||
---|---|---|
| ||
This feature is available for the Jira server deployment option only. We plan to add it to the Cloud version in the near future. |
Setting current user as a watcher for the current issue:
...
Code Block | ||
---|---|---|
| ||
watchers = deleteElement(watchers, currentUser()); |
Create issue link
Info | ||
---|---|---|
| ||
This feature is available for the Jira server deployment option only. We plan to add it to the Cloud version in the near future. |
A SIL post-function that links the current issue to another issue by the Relates issue link type:
...
Close sub-tasks and duplicated linked issues when current issue is closedissues when current issue is closed
Info | ||
---|---|---|
| ||
This feature is available for the Jira server deployment option only. We plan to add it to the Cloud version in the near future. |
A SIL post-function that closes all subtasks and duplicated issues for current issue when close issue transition is triggered:
Code Block | ||
---|---|---|
| ||
string[] issues = arraysConcat(subtasks(key), linkedIssues(key, "Duplicates")); for(string issue in issues) { autotransition("Close Issue", issue); } |
Set/Read user property
Info | ||
---|---|---|
| ||
This feature is available for the Jira server deployment option only. We plan to add it to the Cloud version in the near future. |
A SIL post-function that sets the "country" property for the current user and puts it into a text custom field with id customfield_10100:
...
Fast-tracking (auto-transition) an issue through another action if a condition is trueif a condition is true
Info | ||
---|---|---|
| ||
This feature is available for the Jira server deployment option only. We plan to add it to the Cloud version in the near future. |
Using this you can effectively have multiple start states for a workflow, with the initial state depending on, for example priority, reporter, or whatever.
...
Auto-transition parent when all sub-tasks are resolved
Info | ||
---|---|---|
| ||
This feature is available for the Jira server deployment option only. We plan to add it to the Cloud version in the near future. |
Put this SIL post-function on the sub-task workflow on transitions where the workflow could be set, typically Resolve Issue. If all sibling sub-tasks are resolved this will transition the parent issue using the provided action (eg Resolve Issue):
Code Block | ||
---|---|---|
| ||
if(isNull(parent)) { return; } string[] subtasks = subtasks(parent); for(string subtask in subtasks) { if(%subtask%.status != "Resolved") { return; } } //all sub-tasks are resolved so we can transition the parent autotransition("Resolve Issue", parent); |
Fire an event when condition is truean event when condition is true
Info | ||
---|---|---|
| ||
This feature is available for the Jira server deployment option only. We plan to add it to the Cloud version in the near future. |
This SIL post-function can be used for conditional notification of only high priority issues for instance:
...
Clone an issue and link on transition
Info | ||
---|---|---|
| ||
This feature is available for the Jira server deployment option only. We plan to add it to the Cloud version in the near future. |
Yes, this is available in other places, but this method offers a lot of flexibility (at the expense of a fancy GUI).
...
Create one or more sub-tasks on transition, and optionally reopen existing sub-tasks
Info | ||
---|---|---|
| ||
This feature is available for the Jira server deployment option only. We plan to add it to the Cloud version in the near future. |
This SIL post-function function can be used to create several sub-tasks.
...