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 Not Answered
  • Replies replies
    2
  • Subscribers subscribers
    6
  • Views views
    358
  • 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

Defect Link in Requirements not being sent from ALM QC to JIRA

Rathinkumar Kothiya

Hi Everyone,

We are trying to sync  ALM Qc with Jira where i have tried syncing Story with Requirements. Everything is working fine except one field.

i.e. rel.outwards.causes(jira)(target)  -- connected-to-defect Defect(ALM)(source).

When I link a defect to Story in Jira, It becomes visible in ALM.(target to source works fine.)

But when I add any defect link in requirements in ALM side, Data is not reflected in JIRA despite its a bidirectional flow.

Is there something that I should be doing inorder for it to work. 

There is one more question since all rel.outwards.causes, rel.outward.clone etc are individual fields, how can i manage the flow from alm to jira.

Best Regards,

Rathin

  • 0

    Hi Rathin,

    It is hard to answer these questions without full knowledge of the MF Connect builds you are on, and the complete use cases of the types you are trying to sync.

    On the other hand, technically, "rel.outwards.causes, rel.outward.clone"are labels of the issue link, but the goal in identifying them as individual fields is to allow you to whittle out links with other labels. 

    If issue link types aren;t a constraint to your sync, you should pick 'All related items' instead of 'rel.outward.causes'

    I'd recommend that you open a Support case against Alm/QC, put 'MF Connect issues with Jira Issue Links Synced to Defects' in the title,

    and reference this thread.

    That way, we can set up a meeting with you and help you.

    Take care

    anil

  • 0 in reply to 

    Hi Anil, thank you for the response, there was no specific requirements. So, I tried using "All related items" but still got the same issue. I have created a support ticket and referenced this thread.

    Regards,

    Rathinkumar

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.