-
Bug
-
Resolution: Fixed
-
Low
-
10.116.0
-
5
-
Severity 3 - Minor
-
No
Issue Summary
A Jira Epic is not being synced to Align as a new Feature after having its JiraKey already synced and replaced in Align once in the past.
Reproducible: YES
Steps to Reproduce
-
- Sync a Jira Epic to JA feature using Project "A", let us call it A-01
- Go to the Jira align Project mapping and remove "A"
- As a result all the JA Features will lose their Jira Project Field content
- In your JA Feature created in step 1, add another Jira Project to sync, Project "B"
- Wait until it syncs with the new JiraKey, B-01
- Remap Project "A" into Jira Align
- Note that now, you have 2 Jira Epics pointing to the same Jira Align Feature (A-01 and B-01)
- Now try to delete manually the Web link in Jira Epic A-01 in order to re-sync this issue to JA as a new Feature
- Try to force the sync from Jira to Align.
- Note that A-01 don't sync anymore to Align in anyway and on their Splunk last event it presents an "Child Feature, not updating" event like the one below:
Level: Warning MessageTemplate: Child Feature, not updating Properties: { [-] Action: RunJiraIssueSync Build: 10.119.3.22749 ConnectorId: 1 CorrelationId: 098bfaea4d9c4287b719c0a0dba48d52 CustomJQL: null Customer: Alignsupport Event: IssueTimer IssueId: 14230 IssueKey: VIC-81 JQL: project = 'VIC' AND issuetype = '10000' AND (created >= -26m or updated >= -26m) JiraIssueType: 10000 JiraObjects: CreateEpics JiraProjectKey: VIC MachineName: PA-US-02-CON-CD Method: RunJira_ProcessProject_SyncJiraToAgileCraft ProcessingType: Serial Product: AgileCraft_Jira ServiceName: AgileCraft_Jira_Alignsupport_1 SourceContext: AgileCraft_Jira.AgileCraft ThreadId: 4
Expected Results
My expectation is the Jira EPic A-01 should be able to be synced again into Jira Align
Actual Results
A-01 don't sync anymore to Align in anyway, follow log file:
Level: Warning MessageTemplate: Child Feature, not updating Properties: { [-] Action: RunJiraIssueSync Build: 10.119.3.22749 ConnectorId: 1 CorrelationId: 098bfaea4d9c4287b719c0a0dba48d52 CustomJQL: null Customer: Alignsupport Event: IssueTimer IssueId: 14230 IssueKey: VIC-81 JQL: project = 'VIC' AND issuetype = '10000' AND (created >= -26m or updated >= -26m) JiraIssueType: 10000 JiraObjects: CreateEpics JiraProjectKey: VIC MachineName: PA-US-02-CON-CD Method: RunJira_ProcessProject_SyncJiraToAgileCraft ProcessingType: Serial Product: AgileCraft_Jira ServiceName: AgileCraft_Jira_Alignsupport_1 SourceContext: AgileCraft_Jira.AgileCraft ThreadId: 4
Workaround
The current work around is to duplicate the affected Jira Epic on Jira side forcing the creation of a new JiraKay that will sync fine to Jira Align
- mentioned in
-
Page Loading...
- resolves
-
ALIGNSP-19751 Loading...
-
PS-130357 Loading...