Create Project activity

An activity that creates a project in Jira Software.


Create Project activity

Configure the Create Project activity

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

    Drag Create Project activity

General Configuration

Specifies the basic settings for the Create Project 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

Function:
Specifies the activity name that shows in your process.
Accepted Values:
One line of text that can have spaces.
Default Value:
None
Accepts Process Data 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

Function:
Specifies an optional text description for your activity.
Accepted Values:
More than one line of text.
Default Value:
None
Accepts Process Data Variables:
No

Create Project Configuration > Basic Information tab

Specifies the information to create a project in Jira Software.

Figure: Create Project Configuration > Basic Information tab

Create Project Configuration Basic Information tab

Fields

Field NameDefinition

Jira

Function:
Specifies the access token that connects to your Jira Software service.
Accepted 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 Name

Function:
Specifies the name of the project to create.
Accepted Values:
One line of text that can have spaces.
Default Value:
None
Accepts Process Data 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?

Project Lead

Function:
Specifies the user name of the project lead for the project.
Accepted Values:
A user name of the project lead from the list.

When you select the access token from the Jira field, this field shows the user names of the project leads associated with the access token.

Default Value:
None
Accepts Process Data 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?

Project Type

Function:
Specifies the type of project to create.
Accepted Values:
  • Business
  • Service Desk
  • Software

When you select the access token from the Jira field, this field shows the project types 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?

Project Template Key

Function:
Specifies the template to use to create the project.
Accepted Values:
A project template from the list.

When you select the type of project from the Project Type field, this field shows the project templates associated with the project type.

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?

Project Key

Function:
Specifies a unique name of the project key to create.

This key is used as an idendifier of your project.

Accepted Values:
One line of text (a string) that can have letters and numbers, and can not have spaces or special characters:
  • The text value must be in all capital letters (UPPER CASE).
  • Maximum 10 characters.
Default Value:
None
Accepts Process Data Variables:
Yes
Example:
PROJECTV12

Default Assignee

Function:
Specifies to whom the project is assigned by default.
Accepted Values:
  • Unassigned - The project is created without an assignee.
  • Project_Lead - The project is assigned to the project lead.
Default Value:
Unassigned
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?

Project URL

Function:
Specifies the URL of a website to associate with the project.

The external URL is usually a website that is not in Jira Software, such as a SharePoint site or other location on the company's intranet.

Accepted Values:
One line of text (a string) in URL format.
Default Value:
None
Accepts Process Data Variables:
Yes

Project Category

Function:
Specifies the category of the project to create.

The project categories are used to manage projects in one place, and you can use the project categories in advanced search, sort, and filters.

Accepted Values:
A project category from the list.

When you select the access token from the Jira field, this field shows the project categories associated with the access token.

Default Value:
None
Accepts Process Data 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?

Project Description

Function:
Specifies the description of the project.
Accepted Values:
More than one line of text.
Default Value:
None
Accepts Process Data 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?

Create Project Configuration > Store Response tab

Specifies process data variables to store information about the project.

Figure: Create Project Configuration > Store Response tab

Create Project Configuration Store Response tab

Fields

Field NameDefinition

Jira

Function:
Specifies the access token that connects to your Jira Software service.
Accepted 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 Name

Function:
Specifies the name of the project to create.
Accepted Values:
One line of text that can have spaces.
Default Value:
None
Accepts Process Data 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?

Project Lead

Function:
Specifies the user name of the project lead for the project.
Accepted Values:
A user name of the project lead from the list.

When you select the access token from the Jira field, this field shows the user names of the project leads associated with the access token.

Default Value:
None
Accepts Process Data 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?

Project Type

Function:
Specifies the type of project to create.
Accepted Values:
  • Business
  • Service Desk
  • Software

When you select the access token from the Jira field, this field shows the project types 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?

Project Template Key

Function:
Specifies the template to use to create the project.
Accepted Values:
A project template from the list.

When you select the type of project from the Project Type field, this field shows the project templates associated with the project type.

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?

Project ID

Function:
Specifies the process data variable to store the ID of the project.

The project ID comes from Jira Software.

Accepted Values:
A process data variable that accepts a numeric string with no spaces.
Default Value:
None
Accepts Process Data 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?

Project Key

Function:
Specifies a process data variable to store the key of the project.

The project key comes from Jira Software.

Accepted Values:
A process data variable that accepts an alphanumeric string that can have special characters, but no spaces.
Default Value:
None
Accepts Process Data 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?

Project Link

Function:
Specifies a process data variable to store the URL of the project.

The project URL comes from Jira Software.

Accepted Values:
A process data variable that accepts a URL.
Default Value:
None
Accepts Process Data 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?