Add Attachment (Jira Software) activity

An activity that adds an attachment to an issue in Jira Software.


Add Attachment activity

Configure the Add Attachment activity

To configure the Add Attachment 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 Add Attachment activity onto your process.

    Drag Add Attachment activity

General Configuration

Specifies the basic settings for the Add Attachment 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

Source Repository

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

Figure: Source Repository screen

Source Repository screen

Fields

Field NameDefinition

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.

Add Attachment Configuration

Specifies the information to add the attachment to an issue in Jira Software.

Figure: Add Attachment Configuration screen

Add Attachment 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:

Issue Key or ID

Description:
Specifies the key or ID of the issue to add the file as an attachment.

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?

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.

Allowed Values:
A variable.

Format:

  • String

Accepted:

  • Numbers
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?