|
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 
|
- 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
|
- Description:
- Specifies the name of the project to create.
- Allowed Values:
- One line of text (a string).
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?
|
|
Project Lead
|
- Description:
- Specifies the user name of the project lead for the project.
- Allowed 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 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
|
- Description:
- Specifies the type of project to create.
- Allowed 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
|
- Description:
- Specifies the template to use to create the project.
- Allowed 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
|
- Description:
- Specifies a unique name of the project key to create.
This key is used as an idendifier of your project.
- Allowed 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 Variables:
- Yes
- Example:
- PROJECTV12
|
|
Default Assignee
|
- Description:
- Specifies to whom the project is assigned by default.
- Allowed 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
|
- Description:
- 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. - Allowed Values:
- One line of text (a string) in URL format.
- Default Value:
- None
- Accepts Variables:
- Yes
|
|
Project Category
|
- Description:
- 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.
- Allowed 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 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
|
- Description:
- Specifies the description of the project.
- Allowed Values:
- More than one line of text.
- 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?
|
>
Email Notifications 
. 
