RT and JasperReports Server Integration (got it working, anyone interested?)

Hi Everyone,

RT has been my primary tool to manage Tickets and other Requests since 2001 (RT 2.x) and I am still using it everyday. During the last few years I integrated some billing functions into RT (by using custom fields, workflows etc.). As a natural consequence I have reached the point where I need a function I could not find in RT itself: easily manageable print layouts (aka PDFs :wink: ) that can be custom tailored to fit my client’s needs (e.g. grouping by cost unit).

After a few days of work I now have a completely working system that allows me to create pretty, printable Reports from RT using JasperReports Server [1].

It uses RT’s REST API with customizable (query builder) queries and a simple definition (REST Interface URL, Username and Password) to access ticket data from JasperReports Server. I have done so by creating a custom DataSource [2] and a custom QueryExecuter [3] for JasperReports - all you need to know to prepare your data from RT to be used in a Jasper report are the credentials of your instance’s REST Interface and the query builder query you would like to run - you should know all of these if you work with RT regularly :wink:

You can then use tools like iReport [4] to design fantastic reporting templates for your RT data including your logo, graphs and many other cool things.

As you already might have guessed I think I have found a pretty good solution to integrate RT and JasperReports Server. Now I am standing at the point where I wonder

a) If this is interesting to the RT community (found some mails back in 2007)?
b) If anyone of you is interested in joining my efforts to improve the solution?
c) If there is anything else you would like to know about the solution?
d) As a part of the project I have also built a single J2EE component (DAO [5]) to access the RT REST Interface - would you like to see this component to be released independently?

I would be glad to get some feedback from you to see if this will be a cool thing for myself or if it makes sense to create a project for the RT community - I have many cool ideas in the back of my head (like direct integration into the RT web interface).

Looking forward to your answers and sending curious greetings from Cologne

Benjamin

P.S.: As this is a very “developerish” topic I hope it is OK to crosspost this mail…

[1] JasperReports® Server | Jaspersoft Community
[2] JasperReports 6.20.0 - Data Source Sample
[3] http://jasperforge.org/uploads/publish/jasperreportswebsite/trunk/sample.reference/hibernate/index.html#queryexecuters
[4] iReport Designer | Jaspersoft Community
[5] Oracle Java Technologies | Oracle

This sounds like an excellent addition to RT, a tool I myself have been working with since nearly its inception.

Not much of a developer myself, I encourage you to consider at least making this available to the RT community, if not actually folding it into the RT code base.

Cornell D. Green
CIO
CommunIT Solutions
Let’s get Your Technology to WORK!
http://CommunIT.us/helpdeskOn Apr 9, 2012, at 6:39 AM, Benjamin Boksa mailinglists@boksa.de wrote:

Hi Everyone,

RT has been my primary tool to manage Tickets and other Requests since 2001 (RT 2.x) and I am still using it everyday. During the last few years I integrated some billing functions into RT (by using custom fields, workflows etc.). As a natural consequence I have reached the point where I need a function I could not find in RT itself: easily manageable print layouts (aka PDFs :wink: ) that can be custom tailored to fit my client’s needs (e.g. grouping by cost unit).

After a few days of work I now have a completely working system that allows me to create pretty, printable Reports from RT using JasperReports Server [1].

It uses RT’s REST API with customizable (query builder) queries and a simple definition (REST Interface URL, Username and Password) to access ticket data from JasperReports Server. I have done so by creating a custom DataSource [2] and a custom QueryExecuter [3] for JasperReports - all you need to know to prepare your data from RT to be used in a Jasper report are the credentials of your instance’s REST Interface and the query builder query you would like to run - you should know all of these if you work with RT regularly :wink:

You can then use tools like iReport [4] to design fantastic reporting templates for your RT data including your logo, graphs and many other cool things.

As you already might have guessed I think I have found a pretty good solution to integrate RT and JasperReports Server. Now I am standing at the point where I wonder

a) If this is interesting to the RT community (found some mails back in 2007)?
b) If anyone of you is interested in joining my efforts to improve the solution?
c) If there is anything else you would like to know about the solution?
d) As a part of the project I have also built a single J2EE component (DAO [5]) to access the RT REST Interface - would you like to see this component to be released independently?

I would be glad to get some feedback from you to see if this will be a cool thing for myself or if it makes sense to create a project for the RT community - I have many cool ideas in the back of my head (like direct integration into the RT web interface).

Looking forward to your answers and sending curious greetings from Cologne

Benjamin

P.S.: As this is a very “developerish” topic I hope it is OK to crosspost this mail…

[1] JasperReports® Server | Jaspersoft Community
[2] JasperReports 6.20.0 - Data Source Sample
[3] http://jasperforge.org/uploads/publish/jasperreportswebsite/trunk/sample.reference/hibernate/index.html#queryexecuters
[4] iReport Designer | Jaspersoft Community
[5] Oracle Java Technologies | Oracle

List info: The rt-devel Archives

I agree this would be an excellent addition to RT. Is there a project
repository set up somewhere? I would be interested using this and
helping with the project.

RobertOn Mon, Apr 9, 2012 at 6:51 AM, Cornell D. Green cornellgreen@gmail.com wrote:

This sounds like an excellent addition to RT, a tool I myself have been working with since nearly its inception.

Not much of a developer myself, I encourage you to consider at least making this available to the RT community, if not actually folding it into the RT code base.

Cornell D. Green
CIO
CommunIT Solutions
Let’s get Your Technology to WORK!
http://CommunIT.us/helpdesk

On Apr 9, 2012, at 6:39 AM, Benjamin Boksa mailinglists@boksa.de wrote:

Hi Everyone,

RT has been my primary tool to manage Tickets and other Requests since 2001 (RT 2.x) and I am still using it everyday. During the last few years I integrated some billing functions into RT (by using custom fields, workflows etc.). As a natural consequence I have reached the point where I need a function I could not find in RT itself: easily manageable print layouts (aka PDFs :wink: ) that can be custom tailored to fit my client’s needs (e.g. grouping by cost unit).

After a few days of work I now have a completely working system that allows me to create pretty, printable Reports from RT using JasperReports Server [1].

It uses RT’s REST API with customizable (query builder) queries and a simple definition (REST Interface URL, Username and Password) to access ticket data from JasperReports Server. I have done so by creating a custom DataSource [2] and a custom QueryExecuter [3] for JasperReports - all you need to know to prepare your data from RT to be used in a Jasper report are the credentials of your instance’s REST Interface and the query builder query you would like to run - you should know all of these if you work with RT regularly :wink:

You can then use tools like iReport [4] to design fantastic reporting templates for your RT data including your logo, graphs and many other cool things.

As you already might have guessed I think I have found a pretty good solution to integrate RT and JasperReports Server. Now I am standing at the point where I wonder

a) If this is interesting to the RT community (found some mails back in 2007)?
b) If anyone of you is interested in joining my efforts to improve the solution?
c) If there is anything else you would like to know about the solution?
d) As a part of the project I have also built a single J2EE component (DAO [5]) to access the RT REST Interface - would you like to see this component to be released independently?

I would be glad to get some feedback from you to see if this will be a cool thing for myself or if it makes sense to create a project for the RT community - I have many cool ideas in the back of my head (like direct integration into the RT web interface).

Looking forward to your answers and sending curious greetings from Cologne

Benjamin

P.S.: As this is a very “developerish” topic I hope it is OK to crosspost this mail…

[1] JasperReports® Server | Jaspersoft Community
[2] JasperReports 6.20.0 - Data Source Sample
[3] http://jasperforge.org/uploads/publish/jasperreportswebsite/trunk/sample.reference/hibernate/index.html#queryexecuters
[4] iReport Designer | Jaspersoft Community
[5] Oracle Java Technologies | Oracle

List info: The rt-devel Archives


List info: The rt-devel Archives

Wow - Thanks a lot for all of your feedback.

I will try to setup a (github-)repository and some basic instructions about setting up RT4 and JasperServer on Debian 6 by the end of next week (April 22). At the moment I have to catch up on the backlog created while writing the integration toolkit - yesterday I started working on the backlog by sending out the first actual quarterly invoices created with it :smiley:

In the meantime feel free to send me suggestions, tell me about features you would like to see and use cases to be covered so that I can prepare a proposed roadmap as soon as we start! Also I still don’t have a name for the project (my local repository is named jasper-rt which seems very boring) - if you have any cool suggestions please share them :slight_smile:

@mailinglist admins: Is it OK to use the rt-devel mailinglist for the first basic discussions or should I create a separate mailing list?

Thanks a lot for all your answers, I am sure your interest and feedback will help making this a cool tool.

BenjaminAm 09.04.2012 um 13:44 schrieb Robert Blackwell:

I agree this would be an excellent addition to RT. Is there a project
repository set up somewhere? I would be interested using this and
helping with the project.

Robert

On Mon, Apr 9, 2012 at 6:51 AM, Cornell D. Green cornellgreen@gmail.com wrote:

This sounds like an excellent addition to RT, a tool I myself have been working with since nearly its inception.

Not much of a developer myself, I encourage you to consider at least making this available to the RT community, if not actually folding it into the RT code base.

Cornell D. Green
CIO
CommunIT Solutions
Let’s get Your Technology to WORK!
http://CommunIT.us/helpdesk

On Apr 9, 2012, at 6:39 AM, Benjamin Boksa mailinglists@boksa.de wrote:

Hi Everyone,

RT has been my primary tool to manage Tickets and other Requests since 2001 (RT 2.x) and I am still using it everyday. During the last few years I integrated some billing functions into RT (by using custom fields, workflows etc.). As a natural consequence I have reached the point where I need a function I could not find in RT itself: easily manageable print layouts (aka PDFs :wink: ) that can be custom tailored to fit my client’s needs (e.g. grouping by cost unit).

After a few days of work I now have a completely working system that allows me to create pretty, printable Reports from RT using JasperReports Server [1].

It uses RT’s REST API with customizable (query builder) queries and a simple definition (REST Interface URL, Username and Password) to access ticket data from JasperReports Server. I have done so by creating a custom DataSource [2] and a custom QueryExecuter [3] for JasperReports - all you need to know to prepare your data from RT to be used in a Jasper report are the credentials of your instance’s REST Interface and the query builder query you would like to run - you should know all of these if you work with RT regularly :wink:

You can then use tools like iReport [4] to design fantastic reporting templates for your RT data including your logo, graphs and many other cool things.

As you already might have guessed I think I have found a pretty good solution to integrate RT and JasperReports Server. Now I am standing at the point where I wonder

a) If this is interesting to the RT community (found some mails back in 2007)?
b) If anyone of you is interested in joining my efforts to improve the solution?
c) If there is anything else you would like to know about the solution?
d) As a part of the project I have also built a single J2EE component (DAO [5]) to access the RT REST Interface - would you like to see this component to be released independently?

I would be glad to get some feedback from you to see if this will be a cool thing for myself or if it makes sense to create a project for the RT community - I have many cool ideas in the back of my head (like direct integration into the RT web interface).

Looking forward to your answers and sending curious greetings from Cologne

Benjamin

P.S.: As this is a very “developerish” topic I hope it is OK to crosspost this mail…

[1] JasperReports® Server | Jaspersoft Community
[2] JasperReports 6.20.0 - Data Source Sample
[3] http://jasperforge.org/uploads/publish/jasperreportswebsite/trunk/sample.reference/hibernate/index.html#queryexecuters
[4] iReport Designer | Jaspersoft Community
[5] Oracle Java Technologies | Oracle

List info: The rt-devel Archives


List info: The rt-devel Archives

@mailinglist admins: Is it OK to use the rt-devel mailinglist for the
first basic discussions or should I create a separate mailing list?

rt-devel is a perfectly fine place for now. :slight_smile:

@mailinglist admins: Is it OK to use the rt-devel mailinglist for the
first basic discussions or should I create a separate mailing list?

rt-devel is a perfectly fine place for now. :slight_smile:

rt-devel is great, I’d prefer it to cross-posting (although
cross-posting to make an announce of it for people to test is great).

-kevin

Hi Everyone,

it’s done :slight_smile: I have setup two GitHub repositories to host everything you need to run you own RT an JasperReports Server integration:

RT-REST: RT-REST by bboksa
RT-REST is a Java class library to interact with RT: Request Tracker’s REST Interface.

RT-Jasper: RT-Jasper by bboksa
RT-Jasper is a toolkit to integrate RT: Request Tracker as a queryable data source in JasperServer.

Feel free to give the components a try and let me know what you think :slight_smile: I have chosen to drop full installation instructions in favor of a demo system (see the RT-Jasper page for more information) and I assume you already have a RT installation to play with. To learn how to install JasperReports Server please refer to

JasperReports Server - Browse Files at SourceForge.net .

To help you with your questions I’ll try to be around in #rt on irc.perl.org .

I am really curious to see what you will say about my work and I hope there will be enough users using it to ensure a constant flow of great ideas and improvements.

Enjoy the rest of your weekends :slight_smile:

BenjaminAm 11.04.2012 um 13:18 schrieb Benjamin Boksa:

Wow - Thanks a lot for all of your feedback.

I will try to setup a (github-)repository and some basic instructions about setting up RT4 and JasperServer on Debian 6 by the end of next week (April 22). At the moment I have to catch up on the backlog created while writing the integration toolkit - yesterday I started working on the backlog by sending out the first actual quarterly invoices created with it :smiley:

In the meantime feel free to send me suggestions, tell me about features you would like to see and use cases to be covered so that I can prepare a proposed roadmap as soon as we start! Also I still don’t have a name for the project (my local repository is named jasper-rt which seems very boring) - if you have any cool suggestions please share them :slight_smile:

@mailinglist admins: Is it OK to use the rt-devel mailinglist for the first basic discussions or should I create a separate mailing list?

Thanks a lot for all your answers, I am sure your interest and feedback will help making this a cool tool.

Benjamin

Am 09.04.2012 um 13:44 schrieb Robert Blackwell:

I agree this would be an excellent addition to RT. Is there a project
repository set up somewhere? I would be interested using this and
helping with the project.

Robert

On Mon, Apr 9, 2012 at 6:51 AM, Cornell D. Green cornellgreen@gmail.com wrote:

This sounds like an excellent addition to RT, a tool I myself have been working with since nearly its inception.

Not much of a developer myself, I encourage you to consider at least making this available to the RT community, if not actually folding it into the RT code base.

Cornell D. Green
CIO
CommunIT Solutions
Let’s get Your Technology to WORK!
http://CommunIT.us/helpdesk

On Apr 9, 2012, at 6:39 AM, Benjamin Boksa mailinglists@boksa.de wrote:

Hi Everyone,

RT has been my primary tool to manage Tickets and other Requests since 2001 (RT 2.x) and I am still using it everyday. During the last few years I integrated some billing functions into RT (by using custom fields, workflows etc.). As a natural consequence I have reached the point where I need a function I could not find in RT itself: easily manageable print layouts (aka PDFs :wink: ) that can be custom tailored to fit my client’s needs (e.g. grouping by cost unit).

After a few days of work I now have a completely working system that allows me to create pretty, printable Reports from RT using JasperReports Server [1].

It uses RT’s REST API with customizable (query builder) queries and a simple definition (REST Interface URL, Username and Password) to access ticket data from JasperReports Server. I have done so by creating a custom DataSource [2] and a custom QueryExecuter [3] for JasperReports - all you need to know to prepare your data from RT to be used in a Jasper report are the credentials of your instance’s REST Interface and the query builder query you would like to run - you should know all of these if you work with RT regularly :wink:

You can then use tools like iReport [4] to design fantastic reporting templates for your RT data including your logo, graphs and many other cool things.

As you already might have guessed I think I have found a pretty good solution to integrate RT and JasperReports Server. Now I am standing at the point where I wonder

a) If this is interesting to the RT community (found some mails back in 2007)?
b) If anyone of you is interested in joining my efforts to improve the solution?
c) If there is anything else you would like to know about the solution?
d) As a part of the project I have also built a single J2EE component (DAO [5]) to access the RT REST Interface - would you like to see this component to be released independently?

I would be glad to get some feedback from you to see if this will be a cool thing for myself or if it makes sense to create a project for the RT community - I have many cool ideas in the back of my head (like direct integration into the RT web interface).

Looking forward to your answers and sending curious greetings from Cologne

Benjamin

P.S.: As this is a very “developerish” topic I hope it is OK to crosspost this mail…

[1] JasperReports® Server | Jaspersoft Community
[2] JasperReports 6.20.0 - Data Source Sample
[3] http://jasperforge.org/uploads/publish/jasperreportswebsite/trunk/sample.reference/hibernate/index.html#queryexecuters
[4] iReport Designer | Jaspersoft Community
[5] Oracle Java Technologies | Oracle

List info: The rt-devel Archives


List info: The rt-devel Archives

Hi Benjamin,

I’m trying to install your code but got this error while executing ant:

$ant -f rt-jasper-distribution/build.xml clean deploy

compile:
[mkdir] Created dir:
/home/me/bboksa-RT-Jasper-b48cf4b/distribution/rt-jasper-distribution/classes
[javac] /home/me/bboksa-RT-Jasper-b48cf4b/distribution/rt-jasper-distribution/build.xml:14:
warning: ‘includeantruntime’ was not set, defaulting to
build.sysclasspath=last; set to false for repeatable builds
[javac] Compiling 4 source files to
/home/me/bboksa-RT-Jasper-b48cf4b/distribution/rt-jasper-distribution/classes
[javac] /home/me/bboksa-RT-Jasper-b48cf4b/distribution/rt-jasper-distribution/src/de/boksa/jasper/rt/util/JRRTRESTInterfaceQueryExecuterFactory.java:34:
de.boksa.jasper.rt.util.JRRTRESTInterfaceQueryExecuterFactory is not
abstract and does not override abstract method
createQueryExecuter(net.sf.jasperreports.engine.JRDataset,java.util.Map)
in net.sf.jasperreports.engine.query.JRQueryExecuterFactory
[javac] public class JRRTRESTInterfaceQueryExecuterFactory
implements JRQueryExecuterFactory {
[javac] ^
[javac] /home/me/bboksa-RT-Jasper-b48cf4b/distribution/rt-jasper-distribution/src/de/boksa/jasper/rt/util/JRRTRESTInterfaceQueryExecuterFactory.java:44:
method does not override or implement a method from a supertype
[javac] @Override
[javac] ^
[javac] 2 errors

I’m on a Debian Etc and my javac version is 1.6.0_22.

any clues?

thank you in advance

m

Hi Benjamin,

Very cool. I would certainly be interested in this project. This may ameleorate some
of the reporting issues that we have.

Regards,
KenOn Mon, Apr 09, 2012 at 12:39:25PM +0200, Benjamin Boksa wrote:

Hi Everyone,

RT has been my primary tool to manage Tickets and other Requests since 2001 (RT 2.x) and I am still using it everyday. During the last few years I integrated some billing functions into RT (by using custom fields, workflows etc.). As a natural consequence I have reached the point where I need a function I could not find in RT itself: easily manageable print layouts (aka PDFs :wink: ) that can be custom tailored to fit my client’s needs (e.g. grouping by cost unit).

After a few days of work I now have a completely working system that allows me to create pretty, printable Reports from RT using JasperReports Server [1].

It uses RT’s REST API with customizable (query builder) queries and a simple definition (REST Interface URL, Username and Password) to access ticket data from JasperReports Server. I have done so by creating a custom DataSource [2] and a custom QueryExecuter [3] for JasperReports - all you need to know to prepare your data from RT to be used in a Jasper report are the credentials of your instance’s REST Interface and the query builder query you would like to run - you should know all of these if you work with RT regularly :wink:

You can then use tools like iReport [4] to design fantastic reporting templates for your RT data including your logo, graphs and many other cool things.

As you already might have guessed I think I have found a pretty good solution to integrate RT and JasperReports Server. Now I am standing at the point where I wonder

a) If this is interesting to the RT community (found some mails back in 2007)?
b) If anyone of you is interested in joining my efforts to improve the solution?
c) If there is anything else you would like to know about the solution?
d) As a part of the project I have also built a single J2EE component (DAO [5]) to access the RT REST Interface - would you like to see this component to be released independently?

I would be glad to get some feedback from you to see if this will be a cool thing for myself or if it makes sense to create a project for the RT community - I have many cool ideas in the back of my head (like direct integration into the RT web interface).

Looking forward to your answers and sending curious greetings from Cologne

Benjamin

P.S.: As this is a very “developerish” topic I hope it is OK to crosspost this mail…

[1] JasperReports® Server | Jaspersoft Community
[2] JasperReports 6.20.0 - Data Source Sample
[3] http://jasperforge.org/uploads/publish/jasperreportswebsite/trunk/sample.reference/hibernate/index.html#queryexecuters
[4] iReport Designer | Jaspersoft Community
[5] Oracle Java Technologies | Oracle

Hey Benjamin,
So I woke up this morning thinking about sorting out our RT
reporting/billing issues, and the first email I see is yours. Needless
to say, I am very interested!
JLOn Mon, Apr 9, 2012 at 8:51 AM, ktm@rice.edu ktm@rice.edu wrote:

Hi Benjamin,

Very cool. I would certainly be interested in this project. This may ameleorate some
of the reporting issues that we have.

Regards,
Ken

On Mon, Apr 09, 2012 at 12:39:25PM +0200, Benjamin Boksa wrote:

Hi Everyone,

RT has been my primary tool to manage Tickets and other Requests since 2001 (RT 2.x) and I am still using it everyday. During the last few years I integrated some billing functions into RT (by using custom fields, workflows etc.). As a natural consequence I have reached the point where I need a function I could not find in RT itself: easily manageable print layouts (aka PDFs :wink: ) that can be custom tailored to fit my client’s needs (e.g. grouping by cost unit).

After a few days of work I now have a completely working system that allows me to create pretty, printable Reports from RT using JasperReports Server [1].

It uses RT’s REST API with customizable (query builder) queries and a simple definition (REST Interface URL, Username and Password) to access ticket data from JasperReports Server. I have done so by creating a custom DataSource [2] and a custom QueryExecuter [3] for JasperReports - all you need to know to prepare your data from RT to be used in a Jasper report are the credentials of your instance’s REST Interface and the query builder query you would like to run - you should know all of these if you work with RT regularly :wink:

You can then use tools like iReport [4] to design fantastic reporting templates for your RT data including your logo, graphs and many other cool things.

As you already might have guessed I think I have found a pretty good solution to integrate RT and JasperReports Server. Now I am standing at the point where I wonder

a) If this is interesting to the RT community (found some mails back in 2007)?
b) If anyone of you is interested in joining my efforts to improve the solution?
c) If there is anything else you would like to know about the solution?
d) As a part of the project I have also built a single J2EE component (DAO [5]) to access the RT REST Interface - would you like to see this component to be released independently?

I would be glad to get some feedback from you to see if this will be a cool thing for myself or if it makes sense to create a project for the RT community - I have many cool ideas in the back of my head (like direct integration into the RT web interface).

Looking forward to your answers and sending curious greetings from Cologne

Benjamin

P.S.: As this is a very “developerish” topic I hope it is OK to crosspost this mail…

[1] JasperReports® Server | Jaspersoft Community
[2] JasperReports 6.20.0 - Data Source Sample
[3] http://jasperforge.org/uploads/publish/jasperreportswebsite/trunk/sample.reference/hibernate/index.html#queryexecuters
[4] iReport Designer | Jaspersoft Community
[5] Oracle Java Technologies | Oracle

Le 22/04/2012 ? 19:11:23+0200, Benjamin Boksa a �crit
Hi.

it’s done :slight_smile: I have setup two GitHub repositories to host everything you need to run you own RT an JasperReports Server integration:

RT-REST: RT-REST by bboksa
RT-REST is a Java class library to interact with RT: Request Tracker’s REST Interface.

RT-Jasper: RT-Jasper by bboksa
RT-Jasper is a toolkit to integrate RT: Request Tracker as a queryable data source in JasperServer.

Feel free to give the components a try and let me know what you think :slight_smile: I have chosen to drop full installation instructions in favor of a demo system (see the RT-Jasper page for more information) and I assume you already have a RT installation to play with. To learn how to install JasperReports Server please refer to

JasperReports Server - Browse Files at SourceForge.net .

To help you with your questions I’ll try to be around in #rt on irc.perl.org .

I am really curious to see what you will say about my work and I hope there will be enough users using it to ensure a constant flow of great ideas and improvements.

Enjoy the rest of your weekends :slight_smile:

Big thanks for your works.

Two questions before I spend lot of time to understand your works :

1/ What kind of reports can we have (I never heard of jasper, only
the city in Canada ...;-) ). I didn't find your demo jasperserver
...:-(

2/ Is they are anything to modify on the RT server ? 

thanks again.

Regards.
Albert SHIH
DIO b�timent 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
T�l�phone : 01 45 07 76 26/06 86 69 95 71
xmpp: jas@obspm.fr
Heure local/Local time:
jeu 26 avr 2012 21:25:37 CEST

Hi Albert,

you can generate any kind of reports supported by JasperReports Server. RT-Jasper provides the DataSource necessary to query RT for tickets (the ticket’s data can be used in the reports).

Regarding your questions:

  1. See the private mail I sent you.
  2. No.

If you have further questions just let me know.

Greetings from Cologne

BenjaminAm 26.04.2012 um 21:28 schrieb Albert Shih:

Le 22/04/2012 ? 19:11:23+0200, Benjamin Boksa a écrit
Hi.

it’s done :slight_smile: I have setup two GitHub repositories to host everything you need to run you own RT an JasperReports Server integration:

RT-REST: RT-REST by bboksa
RT-REST is a Java class library to interact with RT: Request Tracker’s REST Interface.

RT-Jasper: RT-Jasper by bboksa
RT-Jasper is a toolkit to integrate RT: Request Tracker as a queryable data source in JasperServer.

Feel free to give the components a try and let me know what you think :slight_smile: I have chosen to drop full installation instructions in favor of a demo system (see the RT-Jasper page for more information) and I assume you already have a RT installation to play with. To learn how to install JasperReports Server please refer to

JasperReports Server - Browse Files at SourceForge.net .

To help you with your questions I’ll try to be around in #rt on irc.perl.org .

I am really curious to see what you will say about my work and I hope there will be enough users using it to ensure a constant flow of great ideas and improvements.

Enjoy the rest of your weekends :slight_smile:

Big thanks for your works.

Two questions before I spend lot of time to understand your works :

1/ What kind of reports can we have (I never heard of jasper, only
the city in Canada …:wink: ). I didn’t find your demo jasperserver
:frowning:

2/ Is they are anything to modify on the RT server ?

thanks again.

Regards.

Albert SHIH
DIO bâtiment 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
Téléphone : 01 45 07 76 26/06 86 69 95 71
xmpp: jas@obspm.fr
Heure local/Local time:
jeu 26 avr 2012 21:25:37 CEST

Dear Benjamin,

Thanks for all the hard work.

I have in fact played with Jasper and RT before.

I gave up as the reports I was trying to generate were to do with time worked.

RT seems to have two different places where time is recorded and calculated, and so querying the DB gets complicated.

Does your integration of Jasper with RT make this clearer / easier?

or do you have any example SQL queries for reporting on Time worked in RT?

Thanks so much,

AlexFrom: “Benjamin Boksa” mailinglists@boksa.de
To: “Albert Shih” Albert.Shih@obspm.fr
Cc: rt-users@lists.bestpractical.com
Sent: Thursday, 26 April, 2012 10:59:37 PM
Subject: Re: [rt-users] Announcing RT-REST and RT-Jasper [was: RT and JasperReports Server Integration (got it working, anyone interested?)]

Hi Albert,

you can generate any kind of reports supported by JasperReports Server. RT-Jasper provides the DataSource necessary to query RT for tickets (the ticket’s data can be used in the reports).

Regarding your questions:

  1. See the private mail I sent you.
  2. No.

If you have further questions just let me know.

Greetings from Cologne

Benjamin

wow! Awesome.

I am going to try this immediately.

Thanks so much for the quick reply too.

AlexFrom: “Benjamin Boksa” mailinglists@boksa.de
To: “Alex Rhys-Hurn” alex@itworx.co.ke
Sent: Friday, 27 April, 2012 1:24:03 PM
Subject: Re: [rt-users] Announcing RT-REST and RT-Jasper [was: RT and JasperReports Server Integration (got it working, anyone interested?)]

Hi Alex,

the cool thing about my integration toolkit is, that it does not use SQL at all. It uses the REST Interface (see “Ticket Search”) described here:

http://requesttracker.wikia.com/wiki/REST

Among other data you get the “TimeWorked” field already calculated :wink:

The Queries used in Jasper are written in RTRIQL which itself is a superset of the Query Builder Query Language (which means you can use any Query Builder query from RT you already have).

Looking forward to you feedback

Benjamin

Dear Benjamin,

Thanks for all the hard work.

I have in fact played with Jasper and RT before.

I gave up as the reports I was trying to generate were to do with time worked.

RT seems to have two different places where time is recorded and calculated, and so querying the DB gets complicated.

Does your integration of Jasper with RT make this clearer / easier?

or do you have any example SQL queries for reporting on Time worked in RT?

Thanks so much,

Alex

From: “Benjamin Boksa” < mailinglists@boksa.de >
To: “Albert Shih” < Albert.Shih@obspm.fr >
Cc: rt-users@lists.bestpractical.com
Sent: Thursday, 26 April, 2012 10:59:37 PM
Subject: Re: [rt-users] Announcing RT-REST and RT-Jasper [was: RT and JasperReports Server Integration (got it working, anyone interested?)]

Hi Albert,

you can generate any kind of reports supported by JasperReports Server. RT-Jasper provides the DataSource necessary to query RT for tickets (the ticket’s data can be used in the reports).

Regarding your questions:

  1. See the private mail I sent you.
  2. No.

If you have further questions just let me know.

Greetings from Cologne

Benjamin

(Only sent out a private answer before, reposting to rt-users)

Hi Alex,

the cool thing about my integration toolkit is, that it does not use SQL at all. It uses the REST Interface (see “Ticket Search”) described here:

http://requesttracker.wikia.com/wiki/REST

Among other data you get the “TimeWorked” field already calculated :wink:

The Queries used in Jasper are written in RTRIQL which itself is a superset of the Query Builder Query Language (which means you can use any Query Builder query from RT you already have).

I have also updated the installation instructions on RT-Jasper by bboksa after some feedback (Thx Marco!).

Looking forward to you feedback

BenjaminAm 27.04.2012 um 12:09 schrieb Alex Rhys-Hurn:

Dear Benjamin,

Thanks for all the hard work.

I have in fact played with Jasper and RT before.

I gave up as the reports I was trying to generate were to do with time worked.

RT seems to have two different places where time is recorded and calculated, and so querying the DB gets complicated.

Does your integration of Jasper with RT make this clearer / easier?

or do you have any example SQL queries for reporting on Time worked in RT?

Thanks so much,

Alex

From: “Benjamin Boksa” mailinglists@boksa.de
To: “Albert Shih” Albert.Shih@obspm.fr
Cc: rt-users@lists.bestpractical.com
Sent: Thursday, 26 April, 2012 10:59:37 PM
Subject: Re: [rt-users] Announcing RT-REST and RT-Jasper [was: RT and JasperReports Server Integration (got it working, anyone interested?)]

Hi Albert,

you can generate any kind of reports supported by JasperReports Server. RT-Jasper provides the DataSource necessary to query RT for tickets (the ticket’s data can be used in the reports).

Regarding your questions:

  1. See the private mail I sent you.
  2. No.

If you have further questions just let me know.

Greetings from Cologne

Benjamin

Am 26.04.2012 um 21:28 schrieb Albert Shih:

Le 22/04/2012 ? 19:11:23+0200, Benjamin Boksa a écrit
Hi.

it’s done :slight_smile: I have setup two GitHub repositories to host everything you need to run you own RT an JasperReports Server integration:

RT-REST: RT-REST by bboksa
RT-REST is a Java class library to interact with RT: Request Tracker’s REST Interface.

RT-Jasper: RT-Jasper by bboksa
RT-Jasper is a toolkit to integrate RT: Request Tracker as a queryable data source in JasperServer.

Feel free to give the components a try and let me know what you think :slight_smile: I have chosen to drop full installation instructions in favor of a demo system (see the RT-Jasper page for more information) and I assume you already have a RT installation to play with. To learn how to install JasperReports Server please refer to

JasperReports Server - Browse Files at SourceForge.net .

To help you with your questions I’ll try to be around in #rt on irc.perl.org .

I am really curious to see what you will say about my work and I hope there will be enough users using it to ensure a constant flow of great ideas and improvements.

Enjoy the rest of your weekends :slight_smile:

Big thanks for your works.

Two questions before I spend lot of time to understand your works :

    1/ What kind of reports can we have (I never heard of jasper, only
    the city in Canada ...;-) ). I didn't find your demo jasperserver
    ...:-(

    2/ Is they are anything to modify on the RT server ? 

thanks again.

Regards.

Albert SHIH
DIO bâtiment 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
Téléphone : 01 45 07 76 26/06 86 69 95 71
xmpp: jas@obspm.fr
Heure local/Local time:
jeu 26 avr 2012 21:25:37 CEST

Hi Benjamin,

Sorry to be a bother, but I am really struggling with this install.

The background: The machine is ubuntu 10.04 LTS. I have installed maven with apt-get maven2 I also apt-get install build-essential and apt-get install openjdk-6-jdk. I installed the jasperserver with the combined jasper stack for ubuntu. Jasper is working properly.

I now have connectivity to your servers (there is an undersea fibre cable cut to my coutry at the moment) , my ISP has failed over to other international links.

but now I see all sorts of errors in the first stages of mvn install as below:

Then things fail to build.

I apologise for being dumb with this but I am a networks guy and this is my first time to build any java kind of thing. I have found that I need to remove the .m2 directory and the whole RT-REST directories when I want to clean up and try again.

Any tips are appreciated.

root@core ~/RT-REST# mvn install
[INFO] Scanning for projects…
Downloading: https://services.boksa.de/maven/repositories/boksa/de/boksa/maven/defaults/maven-default-pom/0.1.0/maven-default-pom-0.1.0.pom
4K downloaded (maven-default-pom-0.1.0.pom)
Downloading: https://services.boksa.de/maven/repositories/boksa/org/apache/maven/wagon/wagon-ssh/1.0/wagon-ssh-1.0.pom
[INFO] Unable to find resource ‘org.apache.maven.wagon:wagon-ssh:pom:1.0’ in repository boksa-repository (https://services.boksa.de/maven/repositories/boksa)
Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-ssh/1.0/wagon-ssh-1.0.pom

[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = ‘ad2eb5e1bb1de5e9347cbd9178c9dd8034eb0d0f’; remote = ‘<!DOCTYPE’ - RETRYING
Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-ssh/1.0/wagon-ssh-1.0.pom

[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = ‘67f056ad160d74130ae07ad6133d0c5a55293e2e’; remote = ‘<!DOCTYPE’ - IGNORING
[WARNING] POM for ‘org.apache.maven.wagon:wagon-ssh:pom:1.0:runtime’ is invalid.

Its dependencies (if any) will NOT be available to the current build.
Downloading: https://services.boksa.de/maven/repositories/boksa/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom
[INFO] Unable to find resource ‘org.codehaus.plexus:plexus-utils:pom:1.1’ in repository boksa-repository (https://services.boksa.de/maven/repositories/boksa)
Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom

Downloading: https://services.boksa.de/maven/repositories/boksa/org/codehaus/plexus/plexus/1.0.4/plexus-1.0.4.pom
[INFO] Unable to find resource ‘org.codehaus.plexus:plexus:pom:1.0.4’ in repository boksa-repository (https://services.boksa.de/maven/repositories/boksa)
Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus/1.0.4/plexus-1.0.4.pom

Downloading: https://services.boksa.de/maven/repositories/boksa/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
Downloading: https://services.boksa.de/maven/repositories/boksa/org/apache/maven/wagon/wagon-ssh/1.0/wagon-ssh-1.0.jar
[INFO] Unable to find resource ‘org.codehaus.plexus:plexus-utils:jar:1.1’ in repository boksa-repository (https://services.boksa.de/maven/repositories/boksa)
Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
[INFO] Unable to find resource ‘org.apache.maven.wagon:wagon-ssh:jar:1.0’ in repository boksa-repository (https://services.boksa.de/maven/repositories/boksa)
Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-ssh/1.0/wagon-ssh-1.0.jar

[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = ‘7292de5afb0da59af2adc323dd29f5e62c3a27b6’; remote = ‘<!DOCTYPE’ - RETRYING
Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-ssh/1.0/wagon-ssh-1.0.jar

[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = ‘3e456700be9f7ad363f06d772ee2c2a5ed0e192d’; remote = ‘<!DOCTYPE’ - IGNORING

[INFO] ------------------------------------------------------------------------
[INFO] Building Unnamed - de.boksa.rt:rt-rest:jar:0.0.1-SNAPSHOT
[INFO] task-segment: [install]
[INFO] ------------------------------------------------------------------------
Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.5/maven-resources-plugin-2.5.pom

[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = ‘cd5e7eafb337ebd92081854151223244aab55d67’; remote = ‘<!DOCTYPE’ - RETRYING
Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.5/maven-resources-plugin-2.5.pom

[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = ‘2e6700b21c12955fbf1238b7ba2f5fd36e52690d’; remote = ‘<!DOCTYPE’ - IGNORING
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project’s POM).

Project ID: org.apache.maven.plugins:maven-resources-plugin
POM Location: /root/.m2/repository/org/apache/maven/plugins/maven-resources-plugin/2.5/maven-resources-plugin-2.5.pom

Reason: Not a v4.0.0 POM. for project org.apache.maven.plugins:maven-resources-plugin at /root/.m2/repository/org/apache/maven/plugins/maven-resources-plugin/2.5/maven-resources-plugin-2.5.pom

[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 20 seconds
[INFO] Finished at: Sat Apr 28 19:27:28 UTC 2012
[INFO] Final Memory: 3M/8M
[INFO] ------------------------------------------------------------------------From: “Benjamin Boksa” mailinglists@boksa.de
To: “Alex Rhys-Hurn” alex@itworx.co.ke
Sent: Saturday, 28 April, 2012 3:56:34 PM
Subject: Re: [rt-users] Announcing RT-REST and RT-Jasper [was: RT and JasperReports Server Integration (got it working, anyone interested?)]

Hi Alex,

according to my monitoring system all servers are up and running. If have at least on report of a completely external user who was able to build RT-Jasper just fine. Please check that it isn’t a problem on your side (maybe is is blocked because of the SSL cert used?). Also please check the URL in your browser.

If that does not help I can send you the required file as an attachment to drop in you local maven repository.

Hope that helps :slight_smile:

Greetings from Cologne

Benjamin

Hi Benjamin,

I am having real troubles building the RT-Jasper. It seems a server is down:

[WARNING] Unable to get resource ‘de.boksa.maven.defaults:maven-default-pom:pom:0.1.0’ from repository boksa-repository ( https://services.boksa.de/maven/repositories/boksa ): Error transferring file: Connection timed out

Can you help with that?

Thanks again,

Alex

From: “Benjamin Boksa” < mailinglists@boksa.de >
To: “rt-users” < rt-users@lists.bestpractical.com >
Sent: Friday, 27 April, 2012 2:09:58 PM
Subject: Re: [rt-users] Announcing RT-REST and RT-Jasper [was: RT and JasperReports Server Integration (got it working, anyone interested?)]

(Only sent out a private answer before, reposting to rt-users)

Hi Alex,

the cool thing about my integration toolkit is, that it does not use SQL at all. It uses the REST Interface (see “Ticket Search”) described here:

http://requesttracker.wikia.com/wiki/REST

Among other data you get the “TimeWorked” field already calculated :wink:

The Queries used in Jasper are written in RTRIQL which itself is a superset of the Query Builder Query Language (which means you can use any Query Builder query from RT you already have).

I have also updated the installation instructions on RT-Jasper by bboksa after some feedback (Thx Marco!).

Looking forward to you feedback

Benjamin

Dear Benjamin,

Thanks for all the hard work.

I have in fact played with Jasper and RT before.

I gave up as the reports I was trying to generate were to do with time worked.

RT seems to have two different places where time is recorded and calculated, and so querying the DB gets complicated.

Does your integration of Jasper with RT make this clearer / easier?

or do you have any example SQL queries for reporting on Time worked in RT?

Thanks so much,

Alex

From: “Benjamin Boksa” < mailinglists@boksa.de >
To: “Albert Shih” < Albert.Shih@obspm.fr >
Cc: rt-users@lists.bestpractical.com
Sent: Thursday, 26 April, 2012 10:59:37 PM
Subject: Re: [rt-users] Announcing RT-REST and RT-Jasper [was: RT and JasperReports Server Integration (got it working, anyone interested?)]

Hi Albert,

you can generate any kind of reports supported by JasperReports Server. RT-Jasper provides the DataSource necessary to query RT for tickets (the ticket’s data can be used in the reports).

Regarding your questions:

  1. See the private mail I sent you.
  2. No.

If you have further questions just let me know.

Greetings from Cologne

Benjamin

Dear Benjamin,

Thanks for all the hard work.

I have in fact played with Jasper and RT before.

I gave up as the reports I was trying to generate were to do with time
worked.

RT seems to have two different places where time is recorded and calculated,
and so querying the DB gets complicated.

Does your integration of Jasper with RT make this clearer / easier?

We have a branch that improves situation with TimeTaken in
transactions table. It can be used with RT 4.0. It will be in RT 4.2.

or do you have any example SQL queries for reporting on Time worked in RT?

Thanks so much,

Alex


From: “Benjamin Boksa” mailinglists@boksa.de
To: “Albert Shih” Albert.Shih@obspm.fr
Cc: rt-users@lists.bestpractical.com
Sent: Thursday, 26 April, 2012 10:59:37 PM
Subject: Re: [rt-users] Announcing RT-REST and RT-Jasper [was: RT
and JasperReports Server Integration (got it working, anyone
interested?)]

Hi Albert,

you can generate any kind of reports supported by JasperReports Server.
RT-Jasper provides the DataSource necessary to query RT for tickets (the
ticket’s data can be used in the reports).

Regarding your questions:

  1. See the private mail I sent you.
  2. No.

If you have further questions just let me know.

Greetings from Cologne

Benjamin

Am 26.04.2012 um 21:28 schrieb Albert Shih:

Le 22/04/2012 ? 19:11:23+0200, Benjamin Boksa a écrit
Hi.

it’s done :slight_smile: I have setup two GitHub repositories to host everything you
need to run you own RT an JasperReports Server integration:

RT-REST: RT-REST by bboksa
RT-REST is a Java class library to interact with RT: Request Tracker’s
REST Interface.

RT-Jasper: RT-Jasper by bboksa
RT-Jasper is a toolkit to integrate RT: Request Tracker as a queryable
data source in JasperServer.

Feel free to give the components a try and let me know what you think :slight_smile:
I have chosen to drop full installation instructions in favor of a demo
system (see the RT-Jasper page for more information) and I assume you
already have a RT installation to play with. To learn how to install
JasperReports Server please refer to

JasperReports Server - Browse Files at SourceForge.net
.

To help you with your questions I’ll try to be around in #rt on
irc.perl.org .

I am really curious to see what you will say about my work and I hope
there will be enough users using it to ensure a constant flow of great ideas
and improvements.

Enjoy the rest of your weekends :slight_smile:

Big thanks for your works.

Two questions before I spend lot of time to understand your works :

    1/ What kind of reports can we have (I never heard of jasper, only
    the city in Canada ...;-) ). I didn't find your demo jasperserver
    ...:-(

    2/ Is they are anything to modify on the RT server ?

thanks again.

Regards.

Albert SHIH
DIO bâtiment 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
Téléphone : 01 45 07 76 26/06 86 69 95 71
xmpp: jas@obspm.fr
Heure local/Local time:
jeu 26 avr 2012 21:25:37 CEST

Best regards, Ruslan.

Hi Alex,

have you been able to solve these problems in the meantime? Looks like somethings is wrong with the way you access the web - maybe a proxy or something? I would really like to help, but this seems to be a problem with you environment which makes it hard to give you a good answer :-/

Let me know if there is anything I can do to help you…

Don’t give up! :wink:

BenjaminAm 28.04.2012 um 21:34 schrieb Alex Rhys-Hurn:

Hi Benjamin,

Sorry to be a bother, but I am really struggling with this install.

The background: The machine is ubuntu 10.04 LTS. I have installed maven with apt-get maven2 I also apt-get install build-essential and apt-get install openjdk-6-jdk. I installed the jasperserver with the combined jasper stack for ubuntu. Jasper is working properly.

I now have connectivity to your servers (there is an undersea fibre cable cut to my coutry at the moment), my ISP has failed over to other international links.

but now I see all sorts of errors in the first stages of mvn install as below:

Then things fail to build.

I apologise for being dumb with this but I am a networks guy and this is my first time to build any java kind of thing. I have found that I need to remove the .m2 directory and the whole RT-REST directories when I want to clean up and try again.

Any tips are appreciated.

root@core ~/RT-REST# mvn install
[INFO] Scanning for projects…
Downloading: https://services.boksa.de/maven/repositories/boksa/de/boksa/maven/defaults/maven-default-pom/0.1.0/maven-default-pom-0.1.0.pom
4K downloaded (maven-default-pom-0.1.0.pom)
Downloading: https://services.boksa.de/maven/repositories/boksa/org/apache/maven/wagon/wagon-ssh/1.0/wagon-ssh-1.0.pom
[INFO] Unable to find resource ‘org.apache.maven.wagon:wagon-ssh:pom:1.0’ in repository boksa-repository (https://services.boksa.de/maven/repositories/boksa)
Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-ssh/1.0/wagon-ssh-1.0.pom

[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = ‘ad2eb5e1bb1de5e9347cbd9178c9dd8034eb0d0f’; remote = ‘<!DOCTYPE’ - RETRYING
Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-ssh/1.0/wagon-ssh-1.0.pom

[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = ‘67f056ad160d74130ae07ad6133d0c5a55293e2e’; remote = ‘<!DOCTYPE’ - IGNORING
[WARNING] POM for ‘org.apache.maven.wagon:wagon-ssh:pom:1.0:runtime’ is invalid.

Its dependencies (if any) will NOT be available to the current build.
Downloading: https://services.boksa.de/maven/repositories/boksa/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom
[INFO] Unable to find resource ‘org.codehaus.plexus:plexus-utils:pom:1.1’ in repository boksa-repository (https://services.boksa.de/maven/repositories/boksa)
Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.pom

Downloading: https://services.boksa.de/maven/repositories/boksa/org/codehaus/plexus/plexus/1.0.4/plexus-1.0.4.pom
[INFO] Unable to find resource ‘org.codehaus.plexus:plexus:pom:1.0.4’ in repository boksa-repository (https://services.boksa.de/maven/repositories/boksa)
Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus/1.0.4/plexus-1.0.4.pom

Downloading: https://services.boksa.de/maven/repositories/boksa/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
Downloading: https://services.boksa.de/maven/repositories/boksa/org/apache/maven/wagon/wagon-ssh/1.0/wagon-ssh-1.0.jar
[INFO] Unable to find resource ‘org.codehaus.plexus:plexus-utils:jar:1.1’ in repository boksa-repository (https://services.boksa.de/maven/repositories/boksa)
Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar
[INFO] Unable to find resource ‘org.apache.maven.wagon:wagon-ssh:jar:1.0’ in repository boksa-repository (https://services.boksa.de/maven/repositories/boksa)
Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-ssh/1.0/wagon-ssh-1.0.jar

[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = ‘7292de5afb0da59af2adc323dd29f5e62c3a27b6’; remote = ‘<!DOCTYPE’ - RETRYING
Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-ssh/1.0/wagon-ssh-1.0.jar

[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = ‘3e456700be9f7ad363f06d772ee2c2a5ed0e192d’; remote = ‘<!DOCTYPE’ - IGNORING

[INFO] ------------------------------------------------------------------------
[INFO] Building Unnamed - de.boksa.rt:rt-rest:jar:0.0.1-SNAPSHOT
[INFO] task-segment: [install]
[INFO] ------------------------------------------------------------------------
Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.5/maven-resources-plugin-2.5.pom

[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = ‘cd5e7eafb337ebd92081854151223244aab55d67’; remote = ‘<!DOCTYPE’ - RETRYING
Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-resources-plugin/2.5/maven-resources-plugin-2.5.pom

[WARNING] *** CHECKSUM FAILED - Checksum failed on download: local = ‘2e6700b21c12955fbf1238b7ba2f5fd36e52690d’; remote = ‘<!DOCTYPE’ - IGNORING
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project’s POM).

Project ID: org.apache.maven.plugins:maven-resources-plugin
POM Location: /root/.m2/repository/org/apache/maven/plugins/maven-resources-plugin/2.5/maven-resources-plugin-2.5.pom

Reason: Not a v4.0.0 POM. for project org.apache.maven.plugins:maven-resources-plugin at /root/.m2/repository/org/apache/maven/plugins/maven-resources-plugin/2.5/maven-resources-plugin-2.5.pom

[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 20 seconds
[INFO] Finished at: Sat Apr 28 19:27:28 UTC 2012
[INFO] Final Memory: 3M/8M
[INFO] ------------------------------------------------------------------------

From: “Benjamin Boksa” mailinglists@boksa.de
To: “Alex Rhys-Hurn” alex@itworx.co.ke
Sent: Saturday, 28 April, 2012 3:56:34 PM
Subject: Re: [rt-users] Announcing RT-REST and RT-Jasper [was: RT and JasperReports Server Integration (got it working, anyone interested?)]

Hi Alex,

according to my monitoring system all servers are up and running. If have at least on report of a completely external user who was able to build RT-Jasper just fine. Please check that it isn’t a problem on your side (maybe is is blocked because of the SSL cert used?). Also please check the URL in your browser.

If that does not help I can send you the required file as an attachment to drop in you local maven repository.

Hope that helps :slight_smile:

Greetings from Cologne

Benjamin

Am 28.04.2012 um 12:11 schrieb Alex Rhys-Hurn:

Hi Benjamin,

I am having real troubles building the RT-Jasper. It seems a server is down:

[WARNING] Unable to get resource ‘de.boksa.maven.defaults:maven-default-pom:pom:0.1.0’ from repository boksa-repository (https://services.boksa.de/maven/repositories/boksa): Error transferring file: Connection timed out

Can you help with that?

Thanks again,

Alex

From: “Benjamin Boksa” mailinglists@boksa.de
To: “rt-users” rt-users@lists.bestpractical.com
Sent: Friday, 27 April, 2012 2:09:58 PM
Subject: Re: [rt-users] Announcing RT-REST and RT-Jasper [was: RT and JasperReports Server Integration (got it working, anyone interested?)]

(Only sent out a private answer before, reposting to rt-users)

Hi Alex,

the cool thing about my integration toolkit is, that it does not use SQL at all. It uses the REST Interface (see “Ticket Search”) described here:

http://requesttracker.wikia.com/wiki/REST

Among other data you get the “TimeWorked” field already calculated :wink:

The Queries used in Jasper are written in RTRIQL which itself is a superset of the Query Builder Query Language (which means you can use any Query Builder query from RT you already have).

I have also updated the installation instructions on RT-Jasper by bboksa after some feedback (Thx Marco!).

Looking forward to you feedback

Benjamin

Am 27.04.2012 um 12:09 schrieb Alex Rhys-Hurn:

Dear Benjamin,

Thanks for all the hard work.

I have in fact played with Jasper and RT before.

I gave up as the reports I was trying to generate were to do with time worked.

RT seems to have two different places where time is recorded and calculated, and so querying the DB gets complicated.

Does your integration of Jasper with RT make this clearer / easier?

or do you have any example SQL queries for reporting on Time worked in RT?

Thanks so much,

Alex

From: “Benjamin Boksa” mailinglists@boksa.de
To: “Albert Shih” Albert.Shih@obspm.fr
Cc: rt-users@lists.bestpractical.com
Sent: Thursday, 26 April, 2012 10:59:37 PM
Subject: Re: [rt-users] Announcing RT-REST and RT-Jasper [was: RT and JasperReports Server Integration (got it working, anyone interested?)]

Hi Albert,

you can generate any kind of reports supported by JasperReports Server. RT-Jasper provides the DataSource necessary to query RT for tickets (the ticket’s data can be used in the reports).

Regarding your questions:

  1. See the private mail I sent you.
  2. No.

If you have further questions just let me know.

Greetings from Cologne

Benjamin

Am 26.04.2012 um 21:28 schrieb Albert Shih:

Le 22/04/2012 ? 19:11:23+0200, Benjamin Boksa a écrit
Hi.

it’s done :slight_smile: I have setup two GitHub repositories to host everything you need to run you own RT an JasperReports Server integration:

RT-REST: RT-REST by bboksa
RT-REST is a Java class library to interact with RT: Request Tracker’s REST Interface.

RT-Jasper: RT-Jasper by bboksa
RT-Jasper is a toolkit to integrate RT: Request Tracker as a queryable data source in JasperServer.

Feel free to give the components a try and let me know what you think :slight_smile: I have chosen to drop full installation instructions in favor of a demo system (see the RT-Jasper page for more information) and I assume you already have a RT installation to play with. To learn how to install JasperReports Server please refer to

JasperReports Server - Browse Files at SourceForge.net .

To help you with your questions I’ll try to be around in #rt on irc.perl.org .

I am really curious to see what you will say about my work and I hope there will be enough users using it to ensure a constant flow of great ideas and improvements.

Enjoy the rest of your weekends :slight_smile:

Big thanks for your works.

Two questions before I spend lot of time to understand your works :

    1/ What kind of reports can we have (I never heard of jasper, only
    the city in Canada ...;-) ). I didn't find your demo jasperserver
    ...:-(

    2/ Is they are anything to modify on the RT server ? 

thanks again.

Regards.

Albert SHIH
DIO bâtiment 15
Observatoire de Paris
5 Place Jules Janssen
92195 Meudon Cedex
Téléphone : 01 45 07 76 26/06 86 69 95 71
xmpp: jas@obspm.fr
Heure local/Local time:
jeu 26 avr 2012 21:25:37 CEST