| Button handy |
|---|
| blank | true |
|---|
| color | #0052CC |
|---|
| name | Send Feedback |
|---|
| link | https://docs.google.com/forms/d/e/1FAIpQLScmToBe3vynAlb5fdKwCGxYqnTbDc66sIBgeecG2BuFDuHc7g/viewform?entry.2002826954=moveIssue+-+15485025 |
|---|
| width | auto |
|---|
|
| Table plus |
|---|
| applyColStyleToCell | true |
|---|
| heading | 0 |
|---|
| columnTypes | s,s,s,s |
|---|
| multiple | false |
|---|
| columnAttributes | style="background:#e5e7ea;font-weight:bold,,style="background:#e5e7ea;font-weight:bold, |
|---|
| enableSorting | false |
|---|
|
Syntax | moveIssue(JMoveIssueParams) | Package | | Alias | | Pkg Usage | |
|
Description
| Excerpt |
|---|
|
This routine function helps moving the issue (including sub-tasks, custom/standard fields, attachments) between projects. |
This routine function helps moving the issue (including sub-tasks, custom/standard fields, attachments) between projects. It gives the possibility to move between different projects and workflows by specifying the optional parameters passed in the JMoveIssueParams SIL Type.
...
| Table plus |
|---|
| applyColStyleToCell | true |
|---|
| columnTypes | s,s,s,s |
|---|
| heading | 0 |
|---|
| multiple | false |
|---|
| enableSorting | false |
|---|
|
Parameter name | Type | Required | Description |
|---|
JMoveIssueParams | FieldJMoveIssueParams | No | 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 workflowYes | Predefined structure that takes information like issueToBeMoved, targetProject, targetIssueTypeId, targetIssueStatusId, targetSubtaskIssueTypeId. At a minimu, issueToBeMoved and targetProject need to be provided. |
|
Return Type
String
After the issue has been moved the new issue key is returned.
...
| 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". |
| Info |
|---|
When dealing with obvious mismatches between projects is recommended to specify the correct issue types, statuses available in the project that the issue is going to be moved. In case of something is not mapped correctly in the process, the routine function will return an empty string ("") and a relevant log message will be added. This function can be used as a post function, however, occasionally this can run into some difficulty since it is still processing as part of the workflow operation while simultaneously the issue is getting moved to a different workflow. As a very simple minded person (me, the author of this sentence) once described the scenario “It’s hard to move a box while you are still sitting in it.” Switching the script to a listener can resolve those issues. |
See also
| Filter by label (Content by label) |
|---|
| showLabels | false |
|---|
| max | 25 |
|---|
| showSpace | false |
|---|
| cql | label = "issue_routine" and space = currentSpace ( ) |
|---|
| labels | array_routines |
|---|
|