Verified Answers


If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Verified Answer
  • Replies reply
    1
  • Subscribers subscribers
    6
  • Views views
    426
  • Users 0 members are here
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Synchronisation MF ALM <-> Jira: How to prevent source specific mapping

Thilo Brause

We have Defects in MF ALM that should be synchronized to Jira as Observations.

After the initial creation, all changes should be done in the Observation in Jira and updated back in MF ALM, so the synchronization has to be bi-directional.

However there are also other Observations in Jira (out of different sources) that should not be synchronized to MF ALM.

I can not prevent the creation of Defects using the datasource properties, because in other mappings (for other issue types in Jira) Defects in MF ALM should be created. 

So I would need a Sync Criteria on Observation to only synchronize the objects that have previously been created through the synchronization from MF ALM. Or something similiar.

Any ideas how this can be done?

  • Verified Answer

    +1  

    One way to achieve this is by defining the type-level direction as uni-directional -> items will be created only on one side.
    The directions on field-level you set to bi-directional where appropriate.

    -> Items created in one direction, only. updates (of fields) performed in both directions...

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.