Software Engineer at a manufacturing company with 10,001+ employees
Real User
Top 5
Mar 25, 2026
Something that I wish would be improved is that TIBCO Jaspersoft Studio looks like something that was designed in the 1980s. The UI is not user-friendly. Finding things in the solution can be quite tedious, and the exported code does not really follow good programming standards. For example, the use of exceptions were not very descriptive. You would have something called exception one, two, three, post-grass exception one, two, three, nothing very descriptive as to what was going on. The files were very long and you would end up with a bunch of code that was not really being used. Helping the tool create more intuitive naming conventions would be better. Maybe implementing some sort of AI logic to clean up the code after it has been generated would help. It would be nice if there was easier integration with other programming languages such as Python, which is where we were migrating to because of its versatility and big data capabilities. Something like Scala and Hadoop would have made it easier for us to remain in Java. I would say to improve TIBCO Jaspersoft, integrate it with other programming languages and other big data tools and include AI functionality. I cannot even see what I need to see in the display box, so I would fix the AI. Another thing to note is that TIBCO Jaspersoft does not offer much in terms of documentation. There were only some wiki pages for some common errors. Customer support required you to have a license. It is not available to the general public. As for performance, working with Java 8 and 11 instead of the latest Java versions is also something that impacted our performance because we had some packages that were dependent on Java version 21 and up.
The integration of TIBCO Jaspersoft with some data sources has limitations that I encountered, and it was not very straightforward. This was one of the concerns with TIBCO Jaspersoft. The limitations include compatibility with some drivers where we do not have adequate JDBC drivers, and because of that, I am not able to make the connection pool. I do see a negative side in terms of support. I am a little disappointed because when we report any defect, it takes time to get a resolution. There are also limitations on some connectors where we do not have connectivity established. These are the few issues I faced while using TIBCO Jaspersoft.
The most valuable feature is maintaining adaptability without forcing software against its inherent nature. Jaspersoft should focus on user interaction features, and one should not expect it to suit every niche.
Senior Statistician at Namibia University of Science and Technology
Real User
Sep 5, 2023
I would like to see some analysis done prior to data extraction. The data extraction itself could also be improved. It should show which data is ready for conduction.
Data Scientist at a tech services company with 51-200 employees
MSP
Feb 28, 2023
For over ten years, the server was developed in Java, using the Java Spring Framework. Last year, I used version 8.0.0 and I did not think it was very good. Currently, it is a Spring Boot, which is new in our framework. I think it is in use because of the legacy of the previous versions, which can sometimes be problematic. Last year, I used a server from a rest service part. We have an in-house front-end service, and TIBCO Jaspersoft was the backend service, we used to store reports and execute reports over the rest of it, but there were many problems. Currently, JSON format is the main format we use, however, in TIBCO Jaspersoft, XML format is the default and JSON did not work because TIBCO did not fix it. For the development part, I think the best thing to do is to make a new server on some other framework. I will not upgrade the old Spring, which is version 8.0.0. That is my opinion. I will create a new server from scratch and copy stuff from the old servers, but not upgrade because the old legacy stuff will then become lost.
BI/ML Team Lead at a tech services company with 501-1,000 employees
Real User
Jan 24, 2023
We have experienced session issues with the session management and the user running a report. So the user's environments can be improved, and a better focus should be put on self-service reporting. So a self-service module could help TIBCO go to the next level.
The Ad Hoc Report Writer does not include as many features as Tableau and needs to be improved to meet expectations. You have to write a lot of customized code to match the features of Tableau's dashboard. Performance could be improved.
I would suggest that TIBCO Jaspersoft make improvements to their reports within their reports. In other words, make the market reports in just one click and in one PDF file. In future releases, TIBCO Jaspersoft would benefit from enabling you to run multiple reports in one file and incorporating more options related to multiple reports.
TIBCO Jaspersoft provides comprehensive reporting and data analysis tools utilized across various sectors. Known for its versatility and low licensing costs, it supports both on-premises and cloud deployments.TIBCO Jaspersoft is designed to meet diverse reporting needs with capabilities like drag-and-drop functionalities, multi-tenancy, REST API integration, HTML5 charts, and customizable reports. Its open-source nature allows for modifications, and the support for multi-language and dynamic...
Something that I wish would be improved is that TIBCO Jaspersoft Studio looks like something that was designed in the 1980s. The UI is not user-friendly. Finding things in the solution can be quite tedious, and the exported code does not really follow good programming standards. For example, the use of exceptions were not very descriptive. You would have something called exception one, two, three, post-grass exception one, two, three, nothing very descriptive as to what was going on. The files were very long and you would end up with a bunch of code that was not really being used. Helping the tool create more intuitive naming conventions would be better. Maybe implementing some sort of AI logic to clean up the code after it has been generated would help. It would be nice if there was easier integration with other programming languages such as Python, which is where we were migrating to because of its versatility and big data capabilities. Something like Scala and Hadoop would have made it easier for us to remain in Java. I would say to improve TIBCO Jaspersoft, integrate it with other programming languages and other big data tools and include AI functionality. I cannot even see what I need to see in the display box, so I would fix the AI. Another thing to note is that TIBCO Jaspersoft does not offer much in terms of documentation. There were only some wiki pages for some common errors. Customer support required you to have a license. It is not available to the general public. As for performance, working with Java 8 and 11 instead of the latest Java versions is also something that impacted our performance because we had some packages that were dependent on Java version 21 and up.
The integration of TIBCO Jaspersoft with some data sources has limitations that I encountered, and it was not very straightforward. This was one of the concerns with TIBCO Jaspersoft. The limitations include compatibility with some drivers where we do not have adequate JDBC drivers, and because of that, I am not able to make the connection pool. I do see a negative side in terms of support. I am a little disappointed because when we report any defect, it takes time to get a resolution. There are also limitations on some connectors where we do not have connectivity established. These are the few issues I faced while using TIBCO Jaspersoft.
The most valuable feature is maintaining adaptability without forcing software against its inherent nature. Jaspersoft should focus on user interaction features, and one should not expect it to suit every niche.
We must change our JAR file and all our dependencies whenever an upgrade occurs. The upgrades are not easy.
I would like to see some analysis done prior to data extraction. The data extraction itself could also be improved. It should show which data is ready for conduction.
Customization is an area with certain shortcomings in the solution that needs improvement.
For over ten years, the server was developed in Java, using the Java Spring Framework. Last year, I used version 8.0.0 and I did not think it was very good. Currently, it is a Spring Boot, which is new in our framework. I think it is in use because of the legacy of the previous versions, which can sometimes be problematic. Last year, I used a server from a rest service part. We have an in-house front-end service, and TIBCO Jaspersoft was the backend service, we used to store reports and execute reports over the rest of it, but there were many problems. Currently, JSON format is the main format we use, however, in TIBCO Jaspersoft, XML format is the default and JSON did not work because TIBCO did not fix it. For the development part, I think the best thing to do is to make a new server on some other framework. I will not upgrade the old Spring, which is version 8.0.0. That is my opinion. I will create a new server from scratch and copy stuff from the old servers, but not upgrade because the old legacy stuff will then become lost.
We have experienced session issues with the session management and the user running a report. So the user's environments can be improved, and a better focus should be put on self-service reporting. So a self-service module could help TIBCO go to the next level.
The Ad Hoc Report Writer does not include as many features as Tableau and needs to be improved to meet expectations. You have to write a lot of customized code to match the features of Tableau's dashboard. Performance could be improved.
I would suggest that TIBCO Jaspersoft make improvements to their reports within their reports. In other words, make the market reports in just one click and in one PDF file. In future releases, TIBCO Jaspersoft would benefit from enabling you to run multiple reports in one file and incorporating more options related to multiple reports.
The data validation and cleansing functionality need to be improved. I would like to see better support for big data.