QC Synchronizer – Problem setting list value

  • Questions
  • QC Synchronizer - Problem setting list value
Question ID: 104761

We have a QC/ALM Synchronizer integration with another Defect tool (JIRA using Orasi’s JIRA Bridge Adapter) and it uses a field called "Resolution" along with the "Status" of the Defect. In QC, we have a corresponding custom field for Resolution, but our list does not have all of the possible values showing when creating the Link, so I mapped to the ones it had and get errors while synchronizing saying it cannot find a value for Resolution when synch'ing an Issue over to QC.

Any ideas why this is happening?

Marked as spam
Posted by (Questions: 74, Answers: 4)
Asked on December 17, 2012 9:18 pm
Answers (1)
Private answer

It may seem a little strange, but QC uses ''list entities'' that are stored separately to the ''field'' entities. The field is associated with a given list, and the list appears in a drop-down in the GUI when working with the Defect. It is common practice of using QC's Workflow/scripting logic in the GUI to swap out the lists to provide context-sensitive lists. For instance effectively ''hiding'' various possible values from the user when they do not make any sense.

Usually when working with any synchronizing or API (advanced programming interface) record population (as ALM Synchronizer does), it is recommended to create and use a list that is a superset of all of the possible ''Resolution'' list values and make that the ''default'' list (the one associated with the ''Resolution'' entity from the ''Customize'' menu). Then add logic to the GUI behavior to handle Status = ''New'' and set the appropriate short list to ''Resolution'' (on the fly) instead of using the short list as the default.

The API will see the ''default'' list and will be able to set any value -- this assumes that the values being sent from the corresponding Issue in JIRA have ''legal'' value combinations in the various fields as well.

Marked as spam
Posted by (Questions: 3, Answers: 466)
Answered on December 17, 2012 9:21 pm
That worked for me, thanks.
( at December 18, 2012 3:53 pm)