Versions Compared

Old Version 25

changes.mady.by.user Pooja Gopalnaidu

Saved on

compared with

New Version 26

changes.mady.by.user Pooja Gopalnaidu

Saved on

Key

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

Description

This page explains:

  • Migration support details for the app content from server/DC to cloud

  • Differences between the server/DC and cloud version of the app

...

  • username or user ID for user fields such as Assignee, Reporter etc...

  • specific components

  • Versions 

  • Issue security levels

  • Status

  • Labels

  • specific values in custom fields

  • entry substitution variable

  • Epic issue type includes

  • All the above mentioned fields for subtask cloning

Differences between server/ DC and cloud versions of the app

The following table lists the differences between server and cloud versions of the app:

Feature

Server/DC

Cloud

Clone behavior configuration

Supports a property file based configuration

Provides easy to use configuration screen to define clone operations that control the clone behavior

Custom clone operations

Supports a maximum of 16

Supports any number of clone operations

Clone options

  • copy attachments

  • copy watchers

  • copy worklogs

  • copy comments

  • copy subtasks

  • copy subtask estimates

  • copy parent reporter

  • copy parent versions

  • copy links

  • copy epic issues

  • copy epic issue subtasks

  • copy epic issue subtask estimates

Supports all the clone options

Supports all the clone options

Note

Images or any form of media added to rich text editor issue fields are copied to the cloned issue only if Copy attachments is selected. If not, a broken image is displayed in the respective field of the cloned issue.


Mapping fields from original issue to a new value in the target issue conditioned on original issue field values

  • Set target project

  • Set target type

  • Set target component

  • Set target version

  • Set link type

  • Set link direction

Supports mapping all issue fields

For more information, refer to the mapping keys section in Clone properties

Set target version

Supports only:

  • Set target project

  • Set target type 

  • Set target component

    • mapping all issue fields

    Setting standard and custom fields for subtasks

    Supported

    Not supported

    Clone conditions

    • Projects

    • Issue types

    • Status

    • Roles

    Supports all clone conditions

    Supports all clone conditions except Roles

    Clone properties

    • fieldExcludes

    • fieldIncludes

    • ignoreFields

    • projectIncludes

    • issueTypeIncludes

    • retainCommentsOriginalDate

    • retainWorklogsOriginalDate

    • epicIssueTypesIncludes

    Supports all clone properties

    Supports only:

    • Ignore fields (Not applicable to subtasks)

    • Field excludes

    • Project includes

    • Issue type includes

    Post cloning processing

    Functions as expected

    Functions as expected with an exception:

    When the administrator modifies the default link type name in issue linking settings from Cloners to any other name, no link is created between the source and target issues during cloning.

    Bulk Clone

    Supported for Data Center only

    Supported

    Localization

    Not supported

    Supported in Spanish, French, German, and Italian.

    Problem reporting

    If you experience any problems or behavior changes that are unexpected, refer to Help and open a ticket with us. This helps us identify and prioritize fixes and improvements.