Consultant at a tech consulting company with 1-10 employees
Real User
Top 20
Aug 19, 2026
The only improvement needed is when we fetch data for more than one or two years. Since it is completely reliable on the database side, Jaspersoft would require performance improvements. When compared to other vendors such as Power BI, the good note is that Jaspersoft has a data warehouse mechanism where we can connect to multiple Hadoop or big data databases to query and fetch data from those different technologies. When compared to Grafana or ClickHouse, we see that log analysis, application monitoring, and security-related features available in other OEMs could be added to Jaspersoft. This way, it would have a combining of all in a single pane of glass, such as metrics, traces, and logs. On the UI side, a little improvement is required. It should have classy reports or dashboards available, and out-of-the-box reports should be kept for at least APM and log analysis. Since it has not been developed, if there are any future plans, I would recommend including such reports for these solutions.
There are some cons. There is no UI provided for macOS, so macOS users have to rely on Windows machines for designing new reports or modifying existing ones. Additionally, when working with large datasets or complex queries, performance can degrade. The reliance on Windows machines for using Jaspersoft's designer tools is one issue that needs improvement for macOS users. Another point to note is that handling millions of records and complex queries often degrades performance. Community support is good, and I have no complaints about it, but I feel the UI is outdated. There should be new features and improvements, particularly with integrating AI-related functionalities. Governance and security are important, but for users unfamiliar with Jaspersoft, it should be easier to create reports with the help of the existing AI features.
Jaspersoft can be improved in several areas. I think this is a very interesting question with feedback for the product teams. Recently it was acquired by HCL, an Indian service-based company. I feel disappointed with the way it is being handled by the respective company that acquired TIBCO Jaspersoft. When TIBCO owned Jaspersoft, it was really good, but after TIBCO acquired it, I feel the marketing strategies or the product implementation roadmap is not up to the way that I have expected. I have personally logged a couple of product defects and very important features as an active user and had to get those features implemented myself. Documentation certainly requires improvement in terms of setting up Tomcat and how specific environment-related instructions are provided, including JVM settings or setting up source profiles. If the basics can be included in the documentation, it would be much better. Additionally, some of the core installations are not happening in Jaspersoft from the last two versions, version eight and ten. Considering the default product issues, when you install, some of the default config files are not getting generated properly and we have to manually change the files and make sure the installation is working fine after that, which is supposed to work fine with the product. The documentation has to be improved in terms of any bottlenecks. If any issue comes, there should be guidance on how to fix it as this is part of the core installation. One important feature I expect is that though the import and export features are given, they are not working for heavy sizing repositories. My current repository is around close to one terabyte plus and we have a great challenge in getting that entire export into one single export. This is not happening. The kind of storage requirements that we have, even if we have increased the storage requirements, the process runs for eight hours, and if any halt in the system occurs, the entire process gets stuck and everything has to be redone. I have raised a product feature to implement a date-based, a date and time-based import and export facilities. That way you can always take some cut of the data for export and import the same cut of the data for import, which gives greater flexibility and immense balance for production rollouts, especially wherein you cannot have an entire production system down and migrate the entire data into the next system. It will always be like one month or two months prior to export all the prod data into a new system. But that will still be two months delta. As there is no provisioning of two months delta to be taken with date time feature as such, we end up doing manual exports from UI for that particular duration, or we need to redo everything back again. This is a great deal of effort that gets invested in doing these import and export activities.
Software Engineer at a manufacturing company with 10,001+ employees
Real User
Top 5
Mar 25, 2026
The challenges or issues I faced with Jaspersoft that led to the migration include the fact that the tech stack is deprecated and it was very troublesome to upgrade the Java version. Additionally, there was no integration with Python, so we ended up rewriting the whole thing in Python. We still use the JRXMLs for the reports, but we are not using Jaspersoft system for Jaspersoft Studio or anything else. The thing that was particularly frustrating with Jaspersoft was that the code being generated was not exactly following coding standards. A lot of the exceptions were very generic, such as exception one, two, three. It does not have great integration with other systems, which was one of the main reasons that led to the migration. We also struggled with learning how the system worked, and there is not much intuitive documentation or support for that matter. The needed improvements for Jaspersoft include better big data support and integrations with something such as Hadoop or Apache Spark.
Automation Engineer at a tech vendor with 10,001+ employees
Real User
Top 20
Mar 19, 2026
Jaspersoft can be improved if the user interface can be enhanced. There are a lot of options for the text fonts, and all of those are on the right side and they are very small. If that can be improved, then it will be better to use. Apart from the user interface and font options, everything else about Jaspersoft sounds good.
The only area for improvement is that initial implementation takes considerable time and is somewhat complex, requiring someone with specific knowledge to perform it. Apart from that, everything is satisfactory.
Jaspersoft is a versatile business intelligence platform offering reporting, analytics, and data integration capabilities. It empowers businesses to visualize and analyze data efficiently, enhancing decision-making processes and supporting various business requirements seamlessly.Jaspersoft stands out for providing open-source BI solutions that enable users to create sophisticated reports, dashboards, and visualizations. Ideal for integrating analytical capabilities into web and mobile...
The only improvement needed is when we fetch data for more than one or two years. Since it is completely reliable on the database side, Jaspersoft would require performance improvements. When compared to other vendors such as Power BI, the good note is that Jaspersoft has a data warehouse mechanism where we can connect to multiple Hadoop or big data databases to query and fetch data from those different technologies. When compared to Grafana or ClickHouse, we see that log analysis, application monitoring, and security-related features available in other OEMs could be added to Jaspersoft. This way, it would have a combining of all in a single pane of glass, such as metrics, traces, and logs. On the UI side, a little improvement is required. It should have classy reports or dashboards available, and out-of-the-box reports should be kept for at least APM and log analysis. Since it has not been developed, if there are any future plans, I would recommend including such reports for these solutions.
There are some cons. There is no UI provided for macOS, so macOS users have to rely on Windows machines for designing new reports or modifying existing ones. Additionally, when working with large datasets or complex queries, performance can degrade. The reliance on Windows machines for using Jaspersoft's designer tools is one issue that needs improvement for macOS users. Another point to note is that handling millions of records and complex queries often degrades performance. Community support is good, and I have no complaints about it, but I feel the UI is outdated. There should be new features and improvements, particularly with integrating AI-related functionalities. Governance and security are important, but for users unfamiliar with Jaspersoft, it should be easier to create reports with the help of the existing AI features.
Jaspersoft can be improved in several areas. I think this is a very interesting question with feedback for the product teams. Recently it was acquired by HCL, an Indian service-based company. I feel disappointed with the way it is being handled by the respective company that acquired TIBCO Jaspersoft. When TIBCO owned Jaspersoft, it was really good, but after TIBCO acquired it, I feel the marketing strategies or the product implementation roadmap is not up to the way that I have expected. I have personally logged a couple of product defects and very important features as an active user and had to get those features implemented myself. Documentation certainly requires improvement in terms of setting up Tomcat and how specific environment-related instructions are provided, including JVM settings or setting up source profiles. If the basics can be included in the documentation, it would be much better. Additionally, some of the core installations are not happening in Jaspersoft from the last two versions, version eight and ten. Considering the default product issues, when you install, some of the default config files are not getting generated properly and we have to manually change the files and make sure the installation is working fine after that, which is supposed to work fine with the product. The documentation has to be improved in terms of any bottlenecks. If any issue comes, there should be guidance on how to fix it as this is part of the core installation. One important feature I expect is that though the import and export features are given, they are not working for heavy sizing repositories. My current repository is around close to one terabyte plus and we have a great challenge in getting that entire export into one single export. This is not happening. The kind of storage requirements that we have, even if we have increased the storage requirements, the process runs for eight hours, and if any halt in the system occurs, the entire process gets stuck and everything has to be redone. I have raised a product feature to implement a date-based, a date and time-based import and export facilities. That way you can always take some cut of the data for export and import the same cut of the data for import, which gives greater flexibility and immense balance for production rollouts, especially wherein you cannot have an entire production system down and migrate the entire data into the next system. It will always be like one month or two months prior to export all the prod data into a new system. But that will still be two months delta. As there is no provisioning of two months delta to be taken with date time feature as such, we end up doing manual exports from UI for that particular duration, or we need to redo everything back again. This is a great deal of effort that gets invested in doing these import and export activities.
The challenges or issues I faced with Jaspersoft that led to the migration include the fact that the tech stack is deprecated and it was very troublesome to upgrade the Java version. Additionally, there was no integration with Python, so we ended up rewriting the whole thing in Python. We still use the JRXMLs for the reports, but we are not using Jaspersoft system for Jaspersoft Studio or anything else. The thing that was particularly frustrating with Jaspersoft was that the code being generated was not exactly following coding standards. A lot of the exceptions were very generic, such as exception one, two, three. It does not have great integration with other systems, which was one of the main reasons that led to the migration. We also struggled with learning how the system worked, and there is not much intuitive documentation or support for that matter. The needed improvements for Jaspersoft include better big data support and integrations with something such as Hadoop or Apache Spark.
Jaspersoft can be improved if the user interface can be enhanced. There are a lot of options for the text fonts, and all of those are on the right side and they are very small. If that can be improved, then it will be better to use. Apart from the user interface and font options, everything else about Jaspersoft sounds good.
The only area for improvement is that initial implementation takes considerable time and is somewhat complex, requiring someone with specific knowledge to perform it. Apart from that, everything is satisfactory.