Third party apps compatibility

Learn how the Actions app is compatible with other vendors’ apps

The Actions transition screens visible on the Request details view support various fields across different apps.

As of now, Actions is compatible with the following apps:

• Table Grid Next Generation
• Insight - Asset Management
• ScriptRunner

In order to enable the compatibilities, simply add your app’s custom field to the transition in the Actions configuration panel.

Steps

1. Go to Jira administration > Manage Apps.
2. In the Actions section on the left sidebar click Workflow Actions.
3. Fill the necessary fields in the Add or Edit transition section.
4. Add your app’s custom fields into the transition.

   

5. Click Save.

   

Result

Your app’s custom fields are visible on the transitions.

Table Grid Next Generation

With Table Grid Next Generation app you can easily insert tables in various Jira contexts to organize data whilst making it concise and easy to read. Along with its 1.12.6 update you can display and edit the tables directly in the Actions app’s transitions.

Insight - Asset Management

With Insight integration you can display the Insight Object/s custom fields directly on your transition.

ScriptRunner

If you have the ScriptRunner app installed on your instance, you can create your own custom validators for the transitions.

In order to get the validator, add an appropriate REST endpoint in the ScriptRunner. You can use the example below which verifies whether the two fields are different from each other:

import com.onresolve.scriptrunner.runner.rest.common.CustomEndpointDelegate
import groovy.json.JsonBuilder
import groovy.transform.BaseScript
import org.codehaus.jackson.map.ObjectMapper

import javax.ws.rs.core.MultivaluedMap
import javax.ws.rs.core.Response

@BaseScript CustomEndpointDelegate delegate

validate(httpMethod: "POST") { MultivaluedMap queryParams, String body ->
    def mapper = new ObjectMapper()
    def tree = mapper.readTree(body)
    def summary = tree.get("Summary")
    def fieldValue = tree.get("customfield_11100")
    if(fieldValue != null &&  summary!=null) {
         if(summary.asText() != fieldValue.asText()) {
        	return Response.ok().build()
    	}
    }
    return Response.status(400).entity("Invalid ").build()
}

Once you’ve applied the endpoint, you can now insert the Custom Validator URL to the transition - in case of the example above, the URL will look like this:

/rest/scriptrunner/latest/custom/validate

Custom Validator URL in Workflow Actions: