Issue Summary

In the indirect sync, you are supposed to have parents and grandparents' data automatically synced to Jira without directly updating the features.
However, having a capability in between a feature and an epic and changing the capabilities parent epic don't trigger indirect sync to Jira.
Hence not updating the Feature Epic parent in Jira keeping 

This is reproducible yes

Steps to Reproduce

1. Have configured your Connector Epic Parent and Capability Parent custom field sync
2. now sync a feature with a Parent capability A and a grandparent epic BB
3. See the Parent and Grandparent names displayed in Jira
4. Now go back to Jira align to the Parent Capability A and change its Epic parent from BB to BC
5. Note that it will not trigger the indirect sync to Jira and the Jira Epic (Feature) will keep the old Grandparent BB
   1. Note: even if you update the Capability description it'll not trigger the indirect sync
6. Now try to update the Grandparent BC or the Feature description
   1. Note that it'll trigger the indirect sync and bring the correct grand parent to Jira BC 

Expected Results

The indirect sync should be triggered by the capability changes too

Actual Results

No errors or logs exceptions

Capability parent changes don't trigger indirect sync to Jira keeping Jira outdated

...

Workaround

• Force the sync by updating the Feature or the grandparent Epic.