We do not support Alm/QC Design steps in MF Connect... yet...

What exactly is not supported? Because in general, DesignSteps can be used as source in MF Connect:

Additionaly, it is possible to Map DesignSteps to Standalone-IssueTypes in Jira, and the data are transfered correctly:

So from my experiments everything seems to be supported. The "only" challenge is the parent-child-mapping between DesignSteps und TestCases.

my apologies. we do support Design Steps. we don't support Test Steps & Test Runs. .

I replied too soon.

So, my corrected answer is, if you're mapping both Test Case & Design Step, then you 'should' be able to carry the parent child relationship in either direction.

If this isn;t working i'd suggest that you  verify that you are on the 4.4.2 version of MF Connect

- if not, upgrade

 if so, open an alm/qc incident, title 'MF Connect issue with alm/qc design steps parent' and we will work with you to examine your configuration. or capture a defect for r&d - whichever the case may be

take care

anil

Hi Thilo,

In order to do this, you will need to create a new relationship in your Jira Data source, under your new "Design Step" type, to capture the parent information.

Stop any connection which uses your Jira Data Source

Go to Data Sources, and Select your Jira Datasource. Then click relationships and click (+) to add a new relationship:

Then select "Design Step" as the type and enter Parent as the Exposed Property Name

Choose a Trace Type of Undefined and set Referred To Type to TestCase

Scroll to the bottom of your list of relationships and find the DesignStep / Parent relationship.

Click the (+) icon on the right:

Set the Trace Type to Undefined and the Referred To Type to DesignStep

Click OK, then click the blue Save button at the top of the Data Source Relationships tab:

Click the Gear on the top right and click Flush Server Cache

Edit your connection, and edit the type mapping for Design Steps

You will now have a newly available field in the "Jira Field" dropdown called "Parent". Map it to parent-id

Save your changes

In your connection, click the left gear, "Clear Watermarks" then click it again and "Run One Iteration"

When your iteration finishes, the items should be created with correct parentage assigned.

If you have any issues implementing the steps, or would like further clarification / assistance, please log an ALM support case with the description "Assistance configuring subtask parentage for a custom type" and we will assist.

Many Thanks,

Ed

Dear Ed,

thank you for this excellent and detailed explanation. Solved my problem immediately.

I never hand the idea that it was possible to map the Relation "Parent" to the field "parent-id" and let MF Connect do all the work! That is an interesting fact, I will share with my coworkers.

Interesting detail: I didn't even had to define the relation. The "Parent" relation was somehow autocreated as soon as I added the types to the datasource. May not have the exact values as you proposed, but works as expected.

Many Thanks,

   Thilo

Can you share the same for Azure Devops as well..as it looks it is not working and one more thing i observed is even after doing the clear watermarks and deleting all the previous data.. the connect is still not syncing the data and assumes it has already synced the old data

Hi Sudhakar,

After deleting items, clearing the watermarks is insufficient to ensure recreation, removal of the corresponding cross references is needed.

This is a sensitive process. If you can log an incident requesting assistance, we can guide you through this in a meeting

Thanks,

Ed

sure will do thanks