Hi Guillame,

Yes, you need to map the Octane Epic to the Jira Epic.

you also need to map the Octane Release to the Jira Release.

you'd need to add a custom string field to the Octane Epic, and map the Jira fix/versions to this custom string field.

uni-directionally, meaning - from jira to octane.

once you do that, the jira fix versions will sync over to the string field.

if you run into issues, please feel free to open a support incident, and email me with the incident number.

i'll set up a call with you at your convenience.

take care

anil

Hi Anil,

thank you very much for the quick feedback.

In my case the fix version/s of my Epic may have multi releases values. That's why I was thinking to map an Octane field list with multi values.

Which means multiple combinations of releases.

Is this possible?

Thanks

Guillaume

Which means multiple combinations of releases. Is this possible?

I do not know. you can give it a try.

i do see that you are on MF Connect 4.4.

we released 4.4.1 last year, we release 4.4.2 in 2 weeks.

you may want to upgrade 

Octane release reference field and Jira fix version/s field allow multi values.

For example:

Epic Fix Version/s = V1.0, V2.0, V8.0 (we are expecting iterations of this epic for the fix version V1.0 , V2.0 and V8.0)

It is possible to map this when we map the fix version/s field with the Octane release reference field (both allow multi values).

But for the Epic without the release field I don't know what is possible to do.

Thanks

Guillaume

Hi Anil,

Happy to setup a call (available the whole day).

For info, I opened a case (ticket) and I was planning to update this discussion when the ticket will be closed.

Note: I also realised that the synch of Jira fix version/s with Octane Release for the features for example do not work when we apply multi values in Jira side because only a single choice can be applied on the Feature release in Octane side.

A contrario the Octane release for Requirements allows multi values.