Documentation and Knowledge Base
Functional Overview
AI Issue Breakdown for Jira introduces automated issue generation functionality. It exposes a new Generate Issues button in the Issue View screen. Once button is pressed:



The AI engine, used to generate issues is configurable. The app operates in one of two modes:
AI Issue Breakdown Assistant integrates Jira with an external AI provider for issue generation. This can be visualized as follows:

Integration process triggers whenever the Generate Issues button is pressed in the Issue View screen and the form is submitted.
In Cloud AI mode, the integration is done with a model hosted in the Internet.
In Private AI mode, any model can be integrated and no data is sent to the Internet.
The following conditions must be met in order to use AI Issue Breakdown Assistant for Jira:
AI Issue Breakdown Assistant for Jira is installed as a standard application through the Universal Plugin Manager (UPM).
Follow these steps:
AI Issue Breakdown Assistant for Jira Data Center requires that you select the app Integration mode, before you can use it.
There is a separate configuration page available, with all configuration options. To navigate it, go to to the Manage Apps screen, open AI Issue Breakdown Assistant for Jira and select the Configure button.
The following configuration settings are available:
A system administrator may change what issue breakdown templates are available for selection and how breakdown is performed. This allows support for various different use cases, specific to your organization. To change the default behaviour, you may override the settings of the existing templates by modifying the following parameters:

With Private AI mode enabled, you can bring your own AI model as an issue generation engine, used by the application. You will need to configure a simple Groovy integration script, that defines the communication protocol with the AI engine. Without configuring the script, the app will not function properly and will not be able to generate issues. By default, a sample script is available that serves as example – it can be modified or adapted.
The script will be invoked every time when the Generate Issues form is submitted.
Script invocation lifecycle is as follows:
For proper execution the following best practises must be followed:
The following variables are available for use within the script:
/* MODIFY THIS SCRIPT TO INTEGRATE YOUR AI MODEL. THIS IS JUST AN EXAMPLE. */
import com.atlassian.jira.util.json.*
import org.apache.http.entity.StringEntity
def payload = new JSONObject() // Prepare body as per API specification
.put("model", "gpt-4o")
.put("messages", new JSONArray()
.put(new JSONObject()
.put("role", "system")
.put("content", issueContext))
.put(new JSONObject()
.put("role", "user")
.put("content", query)))
.put("temperature", 1.0)
.toString();
logger.debug("Preparing POST body: " + payload)
def post = httpClient.newPost("https://api.openai.com/v1/chat/completions") // Create a new request to specified URL
post.setEntity(new StringEntity(payload, java.nio.charset.StandardCharsets.UTF_8)); // Set HTTP payload
post.addHeader("Content-Type", "application/json"); // Set HTTP header
post.addHeader("Authorization", "Bearer REPLACE_ME"); // Set HTTP header
JSONObject json = new JSONObject(httpClient.sendRequest(post)) // Parse response as JSON
def result = json.getJSONArray("choices").getJSONObject(0).getJSONObject("message").getString("content") // Traverse JSON tree
return result // This script must always return the produced result

If custom instructions is enabled, you may also choose a Custom template and input your own breakdown instructions



AI Issue Breakdown Assistant for Jira has the following limitations:
To enable logging for AI Issue Breakdown Assistant, go to Jira Adminsitration -> System -> Logging and Profiling and click on Configure under Default loggers. Add the following entry: com.deview_studios.atlassian.jira.dc.ai_issue_generator and set the logging level to DEBUG.
AI Issue Breakdown Assistant for Jira has the following known issues: