...
Configuration Manager for Jira can migrate watchers, and the app would attempt to either match the watchers to existing users or create a new ones if they don’t exist on the target instance.
One scenario where CMJ won’t migrate the watchers would be when unselecting the ‘Project Roles merge option.’
To fix this:,
Rerun the deployment with the 'Project Roles merge option' ON.
Watchers should be forced to be created on the target instance.
| Info |
|---|
If this is not the customer case and they did tick the ‘Project Roles merge option.’ then:', Ensure users have the same usernames on the source and the target instance. If the customer is using an external directory, Jira might not have the rights to create users on the target instance.
|
...
| Filter by label (Content by label) |
|---|
| showLabels | false |
|---|
| max | 5 |
|---|
| spaces | com.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@bc3e0baf |
|---|
| maxCheckbox | false |
|---|
| showSpace | false |
|---|
| sort | modified |
|---|
| showSpacetype | falsepage |
|---|
| reverse | true | type | page
|---|
| labels | kb-troubleshooting-article |
|---|
| cql | label in ( "cmj-action-deploy" , "cmj-action-type-migrate-watchers" , "cmj-troubleshooting-article" , "cmj-product-jira" ) and type = "page" and space = "SUPPORT" | labels | kb-troubleshooting-article |
|---|
|