Update Issue activity

An activity that changes an issue in Jira Software.


Update Issue activity

Configure the Update Issue activity

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

Examples

Prerequisites

Good to Know

How to Start

  1. Open Process Builder.

    For information about how to open this screen, refer to Process Builder.


    Open Process Builder
  2. In Process Builder, in the Activity Library, open the Jira Software tab.

    Open JiraSoftware tab
  3. On the Jira Software tab, drag the Update Issue activity onto your process.

    Drag Update Issue activity

General Configuration

Specifies the basic settings for the Update Issue activity.

Figure: General Configuration screen

General Configuration screen

Good to Know

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

Fields

Field NameDefinition

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

Update Issue Configuration

Specifies the information to change an issue in Jira Software.

Figure: Update Issue Configuration screen

Update Issue Configuration screen

Fields

Field NameDefinition

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:

Create Add Token icon

Opens this Screen:
Access Token for Jira Software
Function of this Screen:
Configure an access token to connect to Jira Software.
Example:
Refer to:

Project

Description:
Specifies the name of the project to change an issue.
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 change.
Allowed Values:
An issue type 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?

Issue Key or ID

Description:
Specifies the key or ID of the issue to change.

The issue key and ID come from Jira Software.

Allowed Values:
An issue key or ID from Jira Software.
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?

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:
Update Issue Configuration > Configure Basic Fields
Function of this Screen:
Configures the default fields for the issue.

Configure Custom Fields

Opens this Screen:
Update Issue Configuration > Configure Custom Fields
Function of this Screen:
Configures the custom fields for the issue.

Update Issue Configuration > Configure Basic Fields

Configures the default fields for the issue.

Figure: Update Issue Configuration > Configure Basic Fields screen

Update Issue Configuration Configure Basic Fields screen

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.

Fields

Field NameDefinition

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 Add icon

Function:
Adds a Store Response row.

Delete Delete icon

Function:
Deletes the selected row.

Update Issue Configuration > Configure Custom Fields

Configures the custom fields for the issue.

Figure: Update Issue Configuration > Configure Custom Fields screen

Update Issue Configuration Configure Custom Fields screen

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 NameDefinition

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 Add icon

Function:
Adds a Store Response row.

Delete Delete icon

Function:
Deletes the selected row.