It's all about the answers!

Ask a question

RQMExcelWordImporter


Simon Norrington (311109) | asked Feb 19 '10, 4:26 a.m.
Hi, I'm trying to use the Excel import tool without much luck. Is there a more comprehensive set on instructions anywhere - other than at https://jazz.net/wiki/bin/view/Main/RQMExcelWordImporter?

Failing that, has anyone got an idiots guide to using the Excel import tool?

31 answers



permanent link
Annika Kortell (31109) | answered Aug 11 '10, 8:06 a.m.
I managed to export from Word to a file a couple of times, but now nothing happens when I click Export. No progress, no errormessage, nothing.
I have restarted the computer, changed mappingfiles etc, but I cannot get any sign of action, or any output.
Where do I start searching? Anyone else with this problem?
Version 1.0.3729.28369.

permanent link
Jayita Das (6) | answered Oct 05 '10, 12:39 a.m.
I am getting similar error


10/5/2010 8:53:20 AM:
--------------------------------------------------------------------------------
10/5/2010 8:53:20 AM:
SESSION: 10/5/2010 8:53:20 AM

10/5/2010 8:53:20 AM: Getting artifacts from current document Book1.xls
10/5/2010 8:53:20 AM: Created 1 artifacts, sending to server
10/5/2010 8:53:20 AM: sending testscript0 named Book1_PT_ContractorLockingEnhancement_1.xml
10/5/2010 8:53:22 AM: Error sending artifact 0 of type testscript to url https://localhost:9443
10/5/2010 8:53:22 AM: finished writing artifacts

The log says:
10/5/2010 10:02:24 AM: INFO: : response from project has response content key

10/5/2010 10:02:24 AM: INFO: : response has has keys: System.Collections.Hashtable+HashtableEnumerator

10/5/2010 10:02:26 AM: INFO: : RQMConnector: Storing session ID: JSESSIONID=6C6C83BA9A72C80243DF7BDC1438C323; Path=/jazz; Secure,JazzFormAuth=Form; Path=/jazz

10/5/2010 10:02:28 AM: ERROR: : RQMConnector: PutToServer - Error putting resource: https://localhost:9443/jazz/secure/service/com.ibm.rqm.integration.service.IIntegrationService/resources/DSM+/testscript/Book1_PT_ContractorLockingEnhancement_1.xml

10/5/2010 10:02:28 AM: EXCEPTION: : The remote server returned an error: (400) Bad Request.

10/5/2010 10:02:28 AM: at System.Net.HttpWebRequest.GetResponse()
at Mso2Rqm_Common.RQMConnector.PutToServer(String url, String data)

10/5/2010 10:02:28 AM: ERROR: : The remote server returned an error: (400) Bad Request.

10/5/2010 10:02:28 AM: ERROR: : ExcelExportRepositoryDialog: Error saving to url https://localhost:9443 of type testscript

10/5/2010 10:02:28 AM: EXCEPTION: : Object reference not set to an instance of an object.

10/5/2010 10:02:28 AM: at Mso2Rqm_Common.RQMConnector.PutToServer(String url, String data)
at RQMExcelExporter.ExcelExportRepositoryDialog.doExport(IList`1 artifacts)

My script is :
testscript.XLSStartRow=3

\\testscript.dc:title=B

testscript.title=B

testscript.steps.type="execution"

testscript.steps.description=D

testscript.steps.title=A

testscript.steps.name=A

testscript.steps.expectedResult=E

\\testscript.steps.actualResult=F

testscript.XLSDelimeter=\n

permanent link
Javier Lisbona (5157) | answered Oct 13 '10, 10:36 a.m.
Hi people,

I'm trying to import a text into the field "Package Information" of a requirement, but I can't do it.

My configuration file is: (cfg)

requirement.XLSStartRow=2
requirement.XLSArtifactID=A
requirement.dc:title=A
requirement.dc:description=C
requirement.jzalm:owner="admin"
requirement.priority=L

The xml file about requirement in RQM is:

<xs:element name="requirement">
<xs:annotation>
<xs:documentation xml:lang="en">
** Depricated ** A feature or desired piece of functionality.
</xs:documentation>
</xs:annotation>
<xs:complexType>
<xs:sequence>
<xs:element ref="dc:identifier">
<xs:annotation>
<xs:documentation xml:lang="en">
An unambiguous reference to the requirement within a given context.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element ref="dc:title">
<xs:annotation>
<xs:documentation xml:lang="en">
A name given to the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element ref="dc:description">
<xs:annotation>
<xs:documentation xml:lang="en">
Summary of the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element ref="alm:updated">
<xs:annotation>
<xs:documentation xml:lang="en">
XML dateTime of the last update of the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element ref="alm:state">
<xs:annotation>
<xs:documentation xml:lang="en">
An ID or name of the current state of the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element ref="dc:creator">
<xs:annotation>
<xs:documentation xml:lang="en">
An entity primarily responsible for making the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element ref="alm:owner">
<xs:annotation>
<xs:documentation xml:lang="en">
The contributor who owns the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="resolver" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
The contributor who resolved the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="priority" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
The importance of the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="reviewStatus" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
String representing the status of the review.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element ref="alm:suspectStatus">
<xs:annotation>
<xs:documentation xml:lang="en">
The trace status of the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="creationtime" type="xs:dateTime">
<xs:annotation>
<xs:documentation xml:lang="en">
XML dateTime of the creation of the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="resolutionTime" type="xs:dateTime">
<xs:annotation>
<xs:documentation xml:lang="en">
XML dateTime of the resolution of the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="externalTag" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
Since 2.0.0.1. A tag which identifies the source of the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="1" minOccurs="0" ref="approvals">
<xs:annotation>
<xs:documentation xml:lang="en">
The approvals associated with the requirement.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="1" minOccurs="0" ref="customAttributes">
<xs:annotation>
<xs:documentation xml:lang="en">
A list of user generated name/value pairs.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element maxOccurs="1" minOccurs="0" ref="risk">
<xs:annotation>
<xs:documentation xml:lang="en">
The risk associated with the requirement. The possible values could be 'Unassigned', 'Very Low', 'Low', 'Medium', 'High', 'Very High'.
The corresponding internal representation is number 0-5.
</xs:documentation>
</xs:annotation>
</xs:element>
<xs:element name="tags" type="xs:string">
<xs:annotation>
<xs:documentation xml:lang="en">
Since 2.0.0.1. Search strings associated with the requirement workitem.
</xs:documentation>
</xs:annotation>
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>

So, is it possible?

Thanks in advance!!

BR,
Javi

permanent link
rich kenny (6) | answered Oct 21 '10, 2:53 a.m.
I had a very same thing happen to me earlier in the year, worked out in the end but I was certainly confused at the start.

permanent link
Ray Braxton (6) | answered Oct 23 '10, 8:33 p.m.
I am also having trouble with this, the difference I have is that I am using a portable version of excel and word. Maybe that is the problem?

permanent link
Timur Markunin (6495166146) | answered Oct 25 '10, 8:04 a.m.
Managed to sort it out myself. The sample reports were invaluable. It's a shame they aren't referenced on the instructions.


Hi,

could you please write where I could find sample reports?

-Timur

permanent link
Timur Markunin (6495166146) | answered Oct 25 '10, 8:09 a.m.
Managed to sort it out myself. The sample reports were invaluable. It's a shame they aren't referenced on the instructions.


Hi,

could you please write where I could find sample reports?

-Timur

permanent link
Joe Lawrance (21) | answered Feb 07 '11, 6:36 a.m.
I have installed (and uninstalled and reinstalled twice more) the Excel Importer, but am not seeing the "RQM" menu item in Excel (it's the 2003 version)

In here...

https://jazz.net/wiki/bin/view/Main/RQMExcelWordImporter?


In the section:

RQM popup does not appear in Excel or Word when clicking on a menu entry

...it says the following:

For Windows XP
Change the locale settings to 'United States' by changing the value under Control Panel -> Regional and Language Options -> Location to 'United States'. Additionally change the 'Standards and formats' to 'English (United States)'.

While I can change the locale (irritating, cos I'm UK-based and have to tweak the US settings), our company set up doesn't allow me to change 'Standards and formats' to 'English (United States)'

Therefore, I haven't gotten as far as actually trying to import anything to RQM!

Is there any way round this, please?

permanent link
Joe Lawrance (21) | answered Feb 07 '11, 6:48 a.m.
While I can change the locale (irritating, cos I'm U-based and have to tweak the US settings), our company set up doesn't allow me to change 'Standards and formats' to 'English (United States)'
Re my previous post, when I checked this option again, "US" did appear, so I uninstalled the Excel Importer and reinstalled it (yet again).

No change.

Still no "RQM" menu option in Excel.

permanent link
Joe Lawrance (21) | answered Feb 07 '11, 7:51 a.m.
Next update.

I downloaded the RQM-Extras-RQMExcelWordImporter-2.0.1.zip file to my own laptop (Vista SP2 and Office 2007)

Both Excel and Word now include "RQM" in the "Add-ins" menu"

What's the workaround for my work XP/Office 2003 configuration...or am I stuck?

Upgrading to Office 2007 isn't an immediate option since we are a software house and have to support a variety of environments.

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.