how to export defect along with attachments and Comments
3 answers
Comments
Really guys, why doesn't RTC have an ability to export comments.
Please, can we have this capability ?
As answered on the other question:
You can export comments (not discussions though) using the Eclipse client (it does not work in the Web UI and you can not yet display comments or discussions as columns in queries).
Use File>Export
Select Team>Work Items and click next
Select a query and click next
Select Add Columns search for comments and add other columns and click finish.
Thanks for the clarification. I was able to get your command-line app set up. However, it's currently dying with this exception:
there is no command provided but there is probably an issue with the API. I have tested it with 4.x up to 6.x. I have no time to look at 3.x in the near future.
Use the Java that comes with RTC as documented. This is likely a Java problem because you use 1.8.
C:\tvalesky\jazz.command.line\WCL_V3.2_20151120\WCL>set JAVA_HOME=C:\Progra~1\IB
Comments
Vladimir,
Would you mind posting that script?
Ralph, I tried that first; I ran into a dead end when Installation Manager wouldn't recognize the version 3.0.1.5 repository as a repository. So the idea of using an external script is appealing.
I don't understand why you think you need an Installation manager. All parts (SDK, Plain Java client libraries, RTC Eclipse client) should be downloadable as plain zip files.
I have not tested with such an old version, so you would have to check if there are API changes.
Any external tool "script" would have to use the Plain java client libraries to get to the data. There is no official http method to download the attachments.
To do this,
You don't have to install the SDK, if you don't want to see the code. You just need a working Eclipse (or even Java), and the Plain Java Client libraries.
The Extensions Workshop also (the newer version at least) mentions to use the zip files as an alternative. Unfortunately the packaged server for 3.x does not come with an ZIP version, however, you don't have to perform the workshop to use the WCL. You only need to setup the Plain Java Client Libraries (unzip) and unzip the WCL. If you need to debug the WCL, you need an Eclipse client to open the source projects. It would be desirable to have the SDK set up for debugging, but it is not strictly required.
If you import the project, you might see build path errors and errors in the dependencies. You might have to fix that.
I insist the people do the extensions workshop SDK setup, because so many miss the point with being able to see the source code from the SDK. And all my code is wrapped into plugin projects that need the SDK, but you can remove that nature.
Sorry, can't post full script due to legal issues. But the clue is to get links and invoke download for them: