It's all about the answers!

Ask a question

How does one create a defect in RTC using screen display values rather than literals?


Simon Varley (34) | asked Jan 20 '16, 10:01 a.m.
Is there a way to use the plain English values rather than RTC literals when creating a defect?

I'm creating an offline defect loader and get a spreadsheet of data from a testing team. They have a Priority column with values "1", "2", etc. and a Severity column with "High", "Medium", "Low" values - both of which are the values one sees in the RTC screens.

I'd like to be able to create a defect (WorkItem) using the plain English value rather than the RTC literal (see below) - so I don't have to maintain a mapping table ("1" -> "priority.literal.l01", etc.) for every field that they need to use for multiple project areas.

Is it possible?

  <oslc_cm:priority rdf:resource="https://rtc:9443/jazz/oslc/enumerations/_gasc4Ju-Ed6cerS9lb5AWw/priority/priority.literal.l01"/>
  <oslc_cm:severity rdf:resource="https://rtc:9443/jazz/oslc/enumerations/_gasc4Ju-Ed6cerS9lb5AWw/severity/severity.literal.l3"/>
 <oslc_cm:priority rdf:resource="https://rtc:9443/jazz/oslc/enumerations/_gasc4Ju-Ed6cerS9lb5AWw/priority/1"/>
  <oslc_cm:severity rdf:resource="https://rtc:9443/jazz/oslc/enumerations/_gasc4Ju-Ed6cerS9lb5AWw/severity/Medium"/>

Accepted answer


permanent link
Ralph Schoon (57.1k23642) | answered Jan 20 '16, 10:45 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
You have to look up the literals matching the display name. See https://rsjazz.wordpress.com/2012/08/20/manipulationg-work-item-enumeration-values/ or the similar code in code in A RTC WorkItem Command Line Version 3.0.
Simon Varley selected this answer as the correct answer

Comments
Simon Varley commented Jan 20 '16, 11:35 a.m.

OK, so the answer is "No you can't use the UI values, you have to use the literals."


However, you can look up the literals by giving the UI values in other queries.

Thanks for the quick reply!


Simon Varley commented Jan 20 '16, 11:53 a.m.

 Is there a way to query all enumerations in one go or do we have to do each set of enumerations one-by-one?

E.g. get the environment enumerations:

 https://server/ccm/oslc/enumerations/_7MxRkEAZEeW0lNu6_hiJEQ/com.fdc.workitem.enumeration.environment

Your answer


Register or to post your answer.