Versions Compared

Version Old Version 9 New Version Current
Changes made by

Jonathan Muse

Jonathan Muse

Saved on

Key

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

...

Description

Excerpt
hiddentrue

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
applyColStyleToCelltrue
columnTypess,s,s,s
heading0
multiplefalse
enableSortingfalse

Parameter name

Type

Required

Description

JMoveIssueParams

JMoveIssueParams

Yes

Predefined structure that takes information like issueToBeMoved, targetProject, targetIssueTypeId, targetIssueStatusId, targetSubtaskIssueTypeId. At a minimu, issueToBeMoved and targetProject need to be provided.

...

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 routine 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.

...