Versions Compared

Key

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

...

Table plus
applyColStyleToCelltrue
columnTypess,s,s,s
heading0
multiplefalse
enableSortingfalse

Parameter name

Type

Required

Description

JMoveIssueParams

Field

NoYes

Description

issueToBeMoved

string

No

The issue to be moved represented by the issue key.

targetProject

string

No

The project key of the target project where the issue will be moved.

targetIssueTypeId

string

No

The issue type available in the target project represented by its id.

targetSubtaskIssueTypeId

string

No

The sub-task issue type (as there can be different issue types for sub-tasks) represented by its id.

targetSubtaskStatusId

string

No

The sub-task status available in the target workflow.

...

Note

The JMoveIssueParams Sil Type covers most of the use cases when moving an issue to another project. Some scenarios like different workflows, different issue types between the initial project of the issue that needs to be moved an the target project are treated by specifying the optional parameters.

Scenario 1: We have equivalent projects and workflows. If this is the case the only params that needs to be specified are the issue to be moved and the target project. This is available for the sub-tasks as well.

Scenario 2: We have different projects and workflows. In this case, we are forced to specify the issue type that is meaningful for our use case available in the target project as well as the new status as the current ones are no longer valid. Sub-task will need the same.

Scenario 3: Even if we have equivalence between projects and workflows we can still specify a new status(or/and issue type) when moving the issue to the target project. for example, you are moving the issue from TestProject to ProjectA and after moving the issue you want to change the status from "ToDo" which is the current one to "StartProgress".

...