Interface with Jazz with REST or with the Java APIs ?
Hi all,
In the company I work for, we're trying to interface a ticketing system with RTC.
We were wondering which direction you'd suggest us to go at this point.
Should we integrate with RTC using the provided Jazz APIs or using the REST capabilities.
It doesn't seem that the REST interface is fully functionnal, can you provide us a status in the implementation for version 2.0?
For instance, it doesn't seem that it supports attachements:
https://jazz.net/wiki/bin/view/Main/ResourceOrientedWorkItems
We have to transfer attachements from our current ticketing system to RTC.
Which of the two ways should we follow to interface RTC for version 2.0 ?
We thank you in advance for your time.
In the company I work for, we're trying to interface a ticketing system with RTC.
We were wondering which direction you'd suggest us to go at this point.
Should we integrate with RTC using the provided Jazz APIs or using the REST capabilities.
It doesn't seem that the REST interface is fully functionnal, can you provide us a status in the implementation for version 2.0?
For instance, it doesn't seem that it supports attachements:
https://jazz.net/wiki/bin/view/Main/ResourceOrientedWorkItems
Create an attachment [not released yet]
JAZZ=projectareas/_vC_OAGt4Ed2yGaLMUWzhyA
curl -D - -k -b $COOKIES -F projectArea=$JAZZ -F content=@$1 $BASE/attachments
We have to transfer attachements from our current ticketing system to RTC.
Which of the two ways should we follow to interface RTC for version 2.0 ?
We thank you in advance for your time.
3 answers
Hi all,
In the company I work for, we're trying to interface a ticketing system with RTC.
We were wondering which direction you'd suggest us to go at this point.
Should we integrate with RTC using the provided Jazz APIs or using the REST capabilities.
It doesn't seem that the REST interface is fully functionnal, can you provide us a status in the implementation for version 2.0?
For instance, it doesn't seem that it supports attachements:
https://jazz.net/wiki/bin/view/Main/ResourceOrientedWorkItems
Create an attachment [not released yet]
JAZZ=projectareas/_vC_OAGt4Ed2yGaLMUWzhyA
curl -D - -k -b $COOKIES -F projectArea=$JAZZ -F content=@$1 $BASE/attachments
We have to transfer attachements from our current ticketing system to RTC.
Which of the two ways should we follow to interface RTC for version 2.0 ?
We thank you in advance for your time.
Hi Adil,
We are trying to collect answer for your above concern. Please stay tuned.
Susan
I assume that your integration is client code that's communicating with the Jazz server, as opposed to a Jazz server extension.
The Java APIs in RTC 1.0 are stable and will continue to be supported in future releases. The REST APIs in RTC 1.0 are not stable, and are expected to change.
-- Todd
Todd Lainhart
Jazz Foundation
The Java APIs in RTC 1.0 are stable and will continue to be supported in future releases. The REST APIs in RTC 1.0 are not stable, and are expected to change.
-- Todd
Todd Lainhart
Jazz Foundation
Hi all,
In the company I work for, we're trying to interface a ticketing system with RTC.
We were wondering which direction you'd suggest us to go at this point.
Should we integrate with RTC using the provided Jazz APIs or using the REST capabilities.
It doesn't seem that the REST interface is fully functionnal, can you provide us a status in the implementation for version 2.0?
For instance, it doesn't seem that it supports attachements:
https://jazz.net/wiki/bin/view/Main/ResourceOrientedWorkItems
Create an attachment [not released yet]
JAZZ=projectareas/_vC_OAGt4Ed2yGaLMUWzhyA
curl -D - -k -b $COOKIES -F projectArea=$JAZZ -F content=@$1 $BASE/attachments
We have to transfer attachements from our current ticketing system to RTC.
Which of the two ways should we follow to interface RTC for version 2.0 ?
We thank you in advance for your time.