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
    897
  • 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

Azure Devops - update status - resolved date

Vianney M

Hello I've a question about status synchronization between HPQC and Azure DevOps.

Imagine the following status : 

HPQC AZURE DEVOPS
NEW NEW
REOPEN ACTIVE
RESOLVED RESOLVED

When de bug Azure devops is resolved, the status of the defect in HP QC is changed to "resolved" ==> OK 

If the tester in HPQC changes the status of the defect in "REOPEN" , the status of the bug in azure devops must be changed in "active".

At this point I've a problem because the status in devops is correctly changed but I've an error message "Resolved Date must be empty" (Microsoft.VSTS.Common.ResolvedDate)

the field "ResolvedDate" is a system field not visible on Azdo screen 

Is there a mean in mf connect to force this system field as empty in calculated value ? I already tried with null, "", and 0000-00-00 but it does'nt work

Thanks for you help

  • 0  

    Hi Vianney.

    Please open a support case for this (ALM/QC support case, clearly stating in title and beginning of description that it is about MF Connect).

    There is a known issue around closed and resolved date in ADO that we are currently analyzing how to best to work around (in a nutshell: some system-defined, non-modifiable trigger rules in ADO do not fire).

  • 0 in reply to   

    Thanks Dominique I'll see with my manager to open the support case :)  And indeed my problem is linked to the known issue you talk about

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.