This is very much possible (e.g.: https://admhelp.microfocus.com/connect/en/latest/Online/Content/Topics/use-case-octane-jira.htm).

Have you run more than just one iteration?
This might need multiple iterations to create all the items for the required items relationships...

Hi Dominique,

thank you for your prompt reply. Yes, I ran it for more than 10 times.

I am already synchronizing the linkage between multiple entities successfully, e.g.:

- Defect and User Story (rel.outward.is.blocked.by <> Linked Items)

- User Story and Epic (Epic Link <> Feature)




But the link you've posted doesn't provide any example on how to synchronize the linkage between a Defect and Feature from ALM Octane to Jira. What field must be mapped? Or how is it done?

Hmm... the way you sync to Jira seems to REQUIRE an epic link on Jira side (which is NOT always required in Jira, normally).

Are you maybe syncing some Octane defects that simply have no link to an Octane Feature (which, if I understand you correctly, are mapped to Jira Epics)? In Octane, a defect does NOT require such a link...

Also, are you syncing to "normal" Jira bugs? Or is the target type on Jira side a custom sub-task (which requires a parent to create)?

To your first statement: Yes, it's a mandatory field in Jira, but not by default. But it's necessary in our company for our way of working. Jira is the leading system regarding issue tracking.
To the second question: Yes, of course, the Defect has an entered value in the field "Feature". Look at the screenshot of the original post.
To your third statement: You're right, in ALM Octane the field "Feature" is not mandatory by default. 
To your 4th question: Yes it's the normal issue type "Bug" in Jira.

I've recently tested the synchronization from Jira to ALM Octane. It's working then, as I've described:

Defect <> Bug

-  Epic Link <> Feature

But it is still not working the other way around.

In this case, please open a support case (for product "ALM Octane", clearly labeling the case as being for "MF Connect").

This kind of sync is nothing out of the ordinary and is working for other customers.

Before doing so, is it possible to set a default value by using calculated values (tab: Project and Rules)? If yes, how?

Use an "Is New" condition for Calc Values and specify the Feature/parent via ID (numeric). If doing this, do NOT also map the feature/parent via the normal type mapping!

You might want to test this approach with in a simpler scenario to be sure you get everything right.

Erm - I assume you are using MF Connect 4.4.2 for this?

Like this: Set Epic Link = 8 ?

Corresponding Jira Object: