Versions Compared

Key

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

When creating and deploying a snapshot, there can be cases where users in the source instance add new data to the issue, such as comments, and we changing the status, modifying the assignee and other fields, etc. We might also need this new additional information to be added to the target instance in these cases.

Configuration Manager for Jira doesn’t change existing issues. The CMJ app only supports two use cases:

...

If the project exists on the target instance, CMJ will deploy only the issues whose keys don’t exist on the target instance; the existing issues will remain unchanged.

\uD83D\

...

uDCD8 Workaround for adding new data to

...

already deployed issues

...

  1. In the target instance, locate the issues that need to be updated with new comments or any other changes.

  2. Go to the source instance and create a new snapshot with the new information.

  3. In the target instance, delete the already existing issues (located in step 1) that must be updated with the new changes.

  4. Deploy the snapshot in the target instance to visualise visualize these new changes on the selected issues.

Now you should be able to view the new comments on the issues.

...

Filter by label (Content by label)
page
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@bc3e0baf
maxCheckboxfalse
showSpacefalse
sortmodified
showSpacetypefalsepage
reversetruetype
labelskb-how-to-article
cqllabel in ( "cmj-action-deploy" , "cmj-action-migrate" , "cmj-action-overwrite" , "cmj-how-to-article" , "cmj-product-jira" ) and type = "page" and space = "SUPPORT"labelskb-how-to-article