Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Div
idProductTOC

On this page

Table of Contents
maxLevel2
excludeOn this page
typeflat
separatorpipe

Description

Create Issue and Create Sub-task post functions support a number of fields for a configuration that help you control when the issue or sub-task should be created and what information is associated with the issue or sub-task once created.

Tip
titleImportant Notes
  • If the issue is not a sub-task, then the Parent Issue is the same as the original issue - the issue that originally started the transition.
  • Unless otherwise indicated, most fields are common to Create Issue and Create Sub-task.

Sections

...

containing field configurations

The configuration screen contains sections of powerful configuration options.

Basic Fields

The following configuration fields are most commonly used by customers.

Table plus
sortColumn1


FieldCreate Issue
(Available)
Create Sub-task
(Available) 
DefaultDescription
Summary(tick)(tick)
Set issue summary field
Description(tick)(tick)
Set issue description field
Environment(tick)(tick)
Set the environment field
Notes(tick)(tick)
Allows the workflow designer to document the post function


Detailed Fields

Configurations within this section help direct where new issues or sub-tasks are created, who they are assigned, amongst other important details associated with the issue and sub-task creation.

Table plus
sortColumn1


FieldCreate Issue
(Available)
Create Sub-task
(Available) 
DefaultDescription
Project(tick)(error)Original projectSet the project when creating issues
Issue type(tick)(tick)Bug or Sub-taskSet issue type
Priority(tick)(tick)Parent's prioritySet priority
Components(tick)(tick)Parent issue's componentsSet components from a comma-separated list of component names
Affected versions(tick)(tick)
Set affected versions from a comma separated list of version names
Fixed versions(tick)(tick)
Set fixed versions from a comma separated list of version names
Security level(tick)(error)NoneSet security level for the issue
Labels(tick)(tick)
List of labels to be set on the new issue
People
Reporter(tick)(tick)Current user

Set reporter

Note

Prior to 7.2 release, the reporter was set to anonymous in the newly created issue or sub-task upon using Create on Transition for Jira during workflow transition. This is addressed with  CSOT-779 and the reporter of the newly created issue or sub-task now matches with that of the parent/original issue.


Assignee(tick)(tick)Parent issue's assigneeSet assignee
Watchers(tick)(tick)
Add watchers from a comma-separated list of user ids
Dates
Due date(tick)(tick)
Set a due date. Use work to exclude non-working days (example: 5 work).
Due date offset(tick)(tick)
Set offset by no. of days. You can use "work" to exclude non-working days from the calculation. For example, "5 work", adjusts the date by 5 working days.
Original Estimate(tick)(tick)
Set original estimate
Remaining estimate(tick)(tick)
Set remaining estimate


Configurations within this section help create and copy links and link types.

Table plus


FieldCreate Issue
(Available)
Create Sub-task
(Available) 
DefaultDescription
Create link(tick)(tick)
Adds a link to another issue after the new issue is created
Create link type(tick)(tick)
Adds a link type from a pre-defined list of link types such as Blocks, Cloners and so on
Create link direction(tick)(tick)
Adds a link direction
Copy links(tick)(tick)All link typesCopy one or more links from the issue key (or keys) provided to the new issue. The new issue key replaces the key specified for the copy. By default, all link types are copied from each issue key specified. Specify a comma-separated list of link types to subset the copy to only those issue types.
Copy link types(tick)(tick)
Copy one or more link types from the issue key (or keys) provided to the new issue.
Copy remote links(tick)(tick)All remote link typesCopy one or more remote links from the issue key (or keys) provided to the new issue. The new issue key replaces the key specified for the copy. By default, all remote link types are copied from each issue key specified. Specify a comma-separated list of remote link types to subset the copy to only those issue types.
Remote link types(tick)(tick)
Add a list of remote link types to subset the copy to only those issue types. By default, all remote link types will be copied from each issue specified. 


Comment & Attachments

This section allows you to control whether or not to associate attachments from the parent or other Issues during creation.  Likewise, you can have similar controls around comments. 

Table plus
sortColumn1


FieldCreate Issue
(Available)
Create Sub-task
(Available) 
DefaultDescription
Copy attachments(tick)(tick)
If specified, attachments are copied from the issue to the new issue after it is created.
Add comment(tick)(tick)
Comment added to new issue after it is created
Comment security(tick)(tick)
Security group or role for the comment. 
Copy parent issue comments(tick)(tick)
If enabled (ON), copies the comments from the parent of the issue that is being transitioned to the newly created issue(s).
Copy original issue comments(tick)(tick)
If enabled (ON), copies the comments from the issue that is being transitioned to the newly created issue(s).
Include transition attachments(tick)(tick)

Copies attachments captured within workflow transition screens to the newly created issue(s). An option is ignored unless this post function follows the update change history post function.



Custom Fields

Configuration settings within this section allow you to copy custom field values from the parent or original Issue.

...