Create Issue activity

An activity that creates an issue, or a subtask if the option to create a subtask is enabled in Jira Software.

Configure the Create Issue activity

To configure the Create Issue activity, do the procedure in this topic.

Examples

(Example) How to Get the Access Token Credentials from Jira Software

Prerequisites

AgilePoint NX OnDemand (public cloud), or AgilePoint NX PrivateCloud or AgilePoint NX OnPremises v8.0 or higher.

Good to Know

To use the Jira Software process activities, your access token must have these credentials:

Activity Name	Required Permissions
Add Assignee	Browse Projects Assign issues
Add Attachment	Browse Projects Create attachments
Add Comments	Browse Projects Add comments
Create Issue	Browse Projects Create issues
Create Project	Administer Jira
Delete Issue	Browse Projects Delete issues
Get Issue Details	Browse Projects
Update Issue	Browse Projects Edit issues
Update Issue Status	Browse Projects Transition issues

For more information, refer to the Jira Software documentation in Third-Party Vendor Documentation.

To send an email notification, click Advanced > Email Notifications .
For more information, refer to Email Notifications screen (Process Activities).
In most text fields, you can use process data variables as an alternative to literal data values.
You can configure whether this activity waits for other activities before it runs.
For more information, refer to How Do I Configure an Activity to Wait for Other Incoming Activities?
This section shows the configuration settings on the configuration screens for this activity. Other configuration settings apply to system activities. For more information, refer to:
Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?

How to Start

Open Process Builder.
For information about how to open this screen, refer to Process Builder.
In Process Builder, in the Activity Library, open the Jira Software tab.
On the Jira Software tab, drag the Create Issue activity onto your process.

General Configuration

Specifies the basic settings for the Create Issue activity.

Good to Know

Documentation for this screen is provided for completeness. The fields are mostly self-explanatory.

Fields

Field Name	Definition
Display Name	Description: Specifies the activity name that shows in your process. Allowed Values: One line of text (a string). Accepted: Letters Numbers Spaces Default Value: None Accepts Variables: No Example: This is a common configuration field that is used in many examples. Refer to: Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.
Description	Description: Specifies an optional text description for your activity. Allowed Values: More than one line of text. Default Value: None Accepts Variables: No

Field Name

Definition

Display Name

Description:

Specifies the activity name that shows in your process.

Allowed Values:

One line of text (a string).

Accepted:

Letters
Numbers
Spaces

Default Value:

None

Accepts Variables:

Example:

This is a common configuration field that is used in many examples. Refer to:

Examples - Step-by-step use case examples, information about what types of examples are provided in the AgilePoint NX Product Documentation, and other resources where you can find more examples.

Description

Description:: Specifies an optional text description for your activity.
Allowed Values:: More than one line of text.
Default Value:: None
Accepts Variables:: No

Create Issue Request Configuration

Specifies the basic information to create an issue or a subtask in Jira Software.

Fields

Field Name	Definition
Jira	Description: Specifies the access token that connects to your Jira Software service. Allowed Values: A list of access tokens configured for your environment. Default Value: None Example: Refer to: (Example) How to Get the Access Token Credentials from Jira Software
Create	Opens this Screen: Access Token for Jira Software Function of this Screen: Configure an access token to connect to Jira Software. Example: Refer to: (Example) How to Get the Access Token Credentials from Jira Software
Project	Description: Specifies the name of the project for which the issue is to be created. Allowed Values: A project name from the list. When you select the access token from the Jira field, this field shows the project names associated with the access token. Default Value: None Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Issue Type	Description: Specifies the type of issue to create. Allowed Values: An issue type from the list. To create a subtask, you must select the subtask option from the list. When you select the project name from the Project field, this field shows the issue types associated with the project. Default Value: None Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Summary	Description: Specifies a description for the Jira Software issue. Allowed Values: More than one line of text. Accepted: 255 characters maximum Default Value: None Accepts Variables: Yes Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Configure Basic Fields	Opens this Screen: Create Issue Request Configuration > Configure Basic Fields Function of this Screen: Configures the default fields for the issue.
Configure Custom Fields	Opens this Screen: Create Issue Request Configuration > Configure Custom Fields Function of this Screen: Configures the custom fields for the issue.
Add Attachment	Description: Specifies whether to add a file as an attachment to the issue from the data source. Allowed Values: Selected - Configures the Source Repository screen to add a file as an attachment to the issue. Deselected - The issue is created without an attachment. Default Value: Deselected

Create Issue Request Configuration > Configure Basic Fields

Configures the default fields for the issue.

Good to Know

This screen shows a list of default fields in the FIELD NAME field that are configured for the project you selected in the Project field.
For a subtask issue type, the value of the Parent field must be the ID or key of the parent issue.

Fields

Field Name	Definition
Field Name	Description: Specifies a field to add to the issue in a key-value pair. When you select a project name in the Project field, the field names associated with the project show in this field. Allowed Values: A field name from the list. For a subtask issue type, the value of the Parent field must be the ID or key of the parent issue. Default Value: None Accepts Variables: No Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Field Value	Description: Specifies the value for the field in a key-value pair. Allowed Values: A number or a text string that can contain spaces. For a subtask issue type, the value of the Parent field must be the ID or key of the parent issue. Default Value: None Accepts Variables: Yes Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Add	Function: Adds a Store Response row.
Delete	Function: Deletes the selected row.

Create Issue Request Configuration > Configure Custom Fields

Configures the custom fields for the issue.

Good to Know

This screen shows a list of custom fields in the FIELD NAME field that are configured for the project you selected in the Project field.

Fields

Field Name	Definition
Field Name	Description: Specifies a field to add to the issue in a key-value pair. When you select a project name in the Project field, the field names associated with the project show in this field. Allowed Values: A field name from the list. Default Value: None Accepts Variables: No Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Field Value	Description: Specifies the value for the field in a key-value pair. Allowed Values: A number or a text string that can contain spaces. Default Value: None Accepts Variables: Yes Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Add	Function: Adds a Store Response row.
Delete	Function: Deletes the selected row.

Source Repository

Specifies the original, or source, location type for your attachment files.

Fields

Field Name	Definition
Source Repository	Opens this Screen: The configuration screen for your document repository. The specific screen that shows depends on your document repository type. For more information, refer to Document Repositories. Function of this Screen: Configures your document repository.

Create Issue Response Configuration

Specifies process data variables to store information about the issue.

Fields

Field Name	Definition
Issue Link	Description: Specifies a process data variable to store the URL of the issue. The issue URL comes from Jira Software. Allowed Values: A process data variable that accepts a URL. Default Value: None Accepts Variables: Yes Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Issue ID	Description: Specifies a process data variable to store the ID of the issue. The issue ID comes from Jira Software. Allowed Values: A process data variable that accepts a numeric string with no spaces or special characters. Default Value: None Accepts Variables: Yes Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Issue Key	Description: Specifies a process data variable to store the key of the issue. The issue key comes from Jira Software. Allowed Values: A process data variable that accepts an alphanumeric string with no spaces or special characters. Hyphens (-) are accepted. Default Value: None Accepts Variables: Yes Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?
Attachment ID	Description: Specifies a process data variable to store the ID for an attachment file associated with the issue. The attachment ID comes from Jira Software. To enable this field, you must select the Add Attachment field on the Create Issue Request Configuration screen. Allowed Values: A process data variable that accepts a numeric string with no spaces or special characters. Default Value: None Accepts Variables: Yes Limitations: Some information about third-party integrations is outside the scope of the AgilePoint NX Product Documentation. It is the responsibility of the vendors who create and maintain these technologies to provide this information. This includes specific business use cases and examples; explanations for third-party concepts; details about the data models and input and output data formats for third-party technologies; and various types of IDs, URL patterns, connection string formats, or other technical information that is specific to the third-party technologies. For more information, refer to Where Can I Find Information and Examples for Third-Party Integrations?