Post function configuration: Create a Linked Issue (JSU)

Learn how to set up a rule to:
1. Create a linked issue.
2. Copy the last comment from the origin issue to the linked issue description.
3. Use a precondition to run the rule only when the origin issue has an assignee.

How to set up the Create a Linked Issue post function

Post function: Create Linked Issue
Documentation
Support
	
IF
	Value Field :
	
Assignee
IS NOT EMPTY
	
Delete
 Add Precondition
Execution
Preconditions must be:	 True
 False

Only perform this post function if precondition is true / false.
Copy or Move Attachments added during Transition - controlled by Custom Field:	
*** always copy attachments ***
*** always copy attachments ***
*** never copy attachments ***
Status Category Changed
Parent
Issue Type
Time Spent
Story Points
Project
Vulnerability
Design
Fix versions
Sentiment
Σ Time Spent
Status Category
Project overview key
Resolution
Project overview status
Goals
Open forms
Submitted forms
Total forms
Resolved
Work Ratio
Last Viewed
Watchers
Restrict to
Images
Created
Sprint
Flagged
Target start
Priority
Target end
[CHART] Date of First Response
[CHART] Time in Status
Labels
Locked forms
Story point estimate
Issue color
Parent Link
Rank
Remaining Estimate
Σ Original Estimate
Affects versions
Linked Issues
Assignee
Updated
Status
Components
Key
Original estimate
Description
Request Type
Epic Name
Epic Status
Epic Color
Epic Link
Time tracking
Start date
Change type
Change risk
Security Level
Change reason
Actual start
Attachment
Σ Remaining Estimate
Actual end
Summary
Creator
Sub-tasks
Reporter
Σ Progress
Development
Team
Organizations
Approvers
Impact
Environment
Due date
Progress
Votes
Comment
Log Work
  Copy  Move

If the specified custom field has a value, the created issue will contain a copy of all the attachments that were added during the transition.
If you select the option Move, the attachment will not be stored on the origin issue.
Copy Existing Attachments - controlled by Custom Field:	
*** always copy attachments ***
*** always copy attachments ***
*** never copy attachments ***
Status Category Changed
Parent
Issue Type
Time Spent
Story Points
Project
Vulnerability
Design
Fix versions
Sentiment
Σ Time Spent
Status Category
Project overview key
Resolution
Project overview status
Goals
Open forms
Submitted forms
Total forms
Resolved
Work Ratio
Last Viewed
Watchers
Restrict to
Images
Created
Sprint
Flagged
Target start
Priority
Target end
[CHART] Date of First Response
[CHART] Time in Status
Labels
Locked forms
Story point estimate
Issue color
Parent Link
Rank
Remaining Estimate
Σ Original Estimate
Affects versions
Linked Issues
Assignee
Updated
Status
Components
Key
Original estimate
Description
Request Type
Epic Name
Epic Status
Epic Color
Epic Link
Time tracking
Start date
Change type
Change risk
Security Level
Change reason
Actual start
Attachment
Σ Remaining Estimate
Actual end
Summary
Creator
Sub-tasks
Reporter
Σ Progress
Development
Team
Organizations
Approvers
Impact
Environment
Due date
Progress
Votes
Comment
Log Work
If the specified custom field has a value, the created issue will contain a copy of all the attachments which existed already on the issue before the transition was executed.
Initial Mandatory Values for the New Issue
Target Project:	
 Inside same project
 Selected project
 Defined by custom field selection
The new issue will be related via:	
 No relation
 Issue Link
 Sub-Task (issue type of the new issue must be a Sub-Task)
 Epic / Issue in Epic
Issue Type:	
 Same as the origin issue
 Selected issue type
Sub-task
Bug
Epic
Story
Sub-task
Task
 Defined by custom field selection
Perform as User:	
 JSU Add-On User
 Initiating User
 Choose user
Issue Assignee:	
origin issue's assignee
origin issue's assignee
origin issue's reporter
target project lead
component lead of target project
component lead of origin project
unassigned
Sub-Functions: Create Linked Issue
Documentation
Support
Modify fields on the origin and new issue.
 Add Configuration


origin issue's assignee
origin issue's reporter
target project lead
component lead of target project
component lead of origin project
unassigned

How to set up the Create a Linked Issue post function

Learn how to set up a rule to:1. Create a linked issue.2. Copy the last comment from the origin issue to the linked issue description.3. Use a precondition to run the rule only when the origin issue has an assignee.

Post function configuration: Create a Linked Issue (JSU)

Learn how to set up a rule to:
1. Create a linked issue.
2. Copy the last comment from the origin issue to the linked issue description.
3. Use a precondition to run the rule only when the origin issue has an assignee.