Loading...
Should an Epic be created in ADO (as a parent of a Feature) where
the Feature is in an ADO Area Path that does sync to JA
the parent Epic is in an ADO Area Path that does not sync to JA,
then the Feature in Jira Align will not have a Parent Epic set (resulting in the field content being empty/blank/showing Select one). This happens because the Epic will not have been created in JA and the Epic must exist in order to set a value in the Parent Epic field of the feature.
Once in this situation any update to the JA Feature results in the next push to ADO removing the Parent Epic that is set against the Feature inside ADO (because the empty status of the field in JA is pushed back into ADO)
Concern has been expressed (by a customer) that creating an ADO Epic in an area path that does not synchronized can sometimes be done deliberately but can also easily happen unintentionally and that for either scenario they don't want the parent epic being removed from a feature on the ADO side just because the field is empty in JA. They don't want to disable Epic sync as there are situations where the ADO Epics are created in area paths that do sync.
Add an ADO connector setting that allows a choice between
Sync the parent field value of Features from JA to ADO when either a valid parent Epic/Capability OR no parent Epic/Capability is set
Sync the parent field value of features from JA to ADO when ONLY a valid parent Epic/Capability is set leaving the ADO value untouched if the field is empty/blank/set to Select one - as there may be instances when the parent is set in Jira Align and removing that parent should remove the parent in ADO as well, this will need an extra Feature setting (or some kind of pop-up) where the status to sync the blank field to ADO clears after a successful sync, to allow a user in Jira Align to control if they want the ADO parent to be removed when the field is blanked
