PLANTA project 26
Version 26 published 12/18/2025: Database 26.0.0, Server 39.1.0, Client 39.5.34.5
Below, release notes on PLANTA project user functions are listed. For release notes on the customizing and interface functions, please refer to the PLANTA customizer and PLANTA link help areas.
The functions and bugfixes listed here are mainly contained in the database software component. Functions which stem from the server or client component are explicitly indicated in the column on the right-hand side. Under Container Releases in the Technology/Installation help area, you will find a comprehensive overview of the PLANTA project releases with links to their corresponding pages as well as information on software installation and update for the release you use.
Here you can find known and fixed issues.
Press CTRL+B in the program or select the ? → System Information menu item to learn which component versions you are using.
DB 26.1.0
Features
Key | Description | Server/Client/Web |
|---|---|---|
Web Client | ||
1344 | In the Web Client, structures and their graphical display are now supported. This means specifically:
The respective objects and functions are available by default starting with database version 26.1.0 and web client version 3.7.0. For information on the implementation of this feature in an older database version, please click here | Web 3.7.0 |
206 | The Change password function has now been activated in the Web Client. The menu item is available by default starting with database version 26.1.0 and web client version 3.7.0. | Web 3.7.0 |
Project/Portfolio | ||
1155 | In the Schedule you can unhide and mark external links by clicking on the arrows in the Gantt chart and, conversely, hide/unmark them. | |
823 825 | Resources that are not to be planned (checkbox Resource to be planned = N) are now grayed out in all resource selection listboxes. This prevents child resources (e.g., department resources) from being automatically hidden. They remain visible and can be selected. | |
1337 | In the Assign Planning Objects to the Portfolio module, only planning objects that can be assigned to the selected portfolio are now displayed. Planning objects that are already assigned to a portfolio with other quality gates will no longer be displayed. | |
1279 | If no project is selected in the listbox as the source for copying in the Copy Schedule module and the Copy Schedule button is clicked on, a message is displayed prompting you to select a project from the listbox. | |
1282 | The Min. Load/Day parameter can now be displayed in the schedule and customized for each project without affecting the global Default Min. Load/Day parameter or other projects. | |
1234 | In the Project Core Data module, the project manager is now categorized under “Core Team” in the Stakeholders section—both when creating a new project and when updating the project manager later. | |
1321 | When you enter hours worked via a time recording link, a corresponding message is displayed in the status bar after you save. | |
1469 | In the Load profile listbox on the resource assignment in the Schedule module, the empty default value is now displayed as „linear load“, so that users can recognize what distribution type the empty value is. | |
1340 1339 1562 | Since only portfolio and multi-portfolio managers are authorized to approve, cancel, and delete budget periods, the corresponding buttons in the Budget module are visible only to users with these authorizations. Furthermore the Cancel Approval per Budget Period function was removed from the module of the same name to the Budget module in the portfolio. The corresponding dialog messages have also been adjusted. The Cancel Approval per Budget Period module has been removed. | |
1437 | Boards that were accidentally synced with a hybrid board and do not yet contain any cards can now be deleted.
If a board already contains cards, the synchronization of a task cannot be canceled, and a corresponding message will be displayed. | |
1503 | The access rights for planning objects have been harmonized: Both „*“ as well as no entry in the Object access field grant the corresponding user read rights to any planning object. | |
1519 | In the Infoboard (Portfolio) module, standardized error messages are now displayed when the required fields are left blank after clicking the buttons in the Objective Contributions and Risk Values area. | |
1561 1553 | Direct link (deep link) to tasks have been implemented in the PLANTA standard system. Clicking the Copy task link button in the header of the Task module copies a direct link to the corresponding task to the clipboard. | |
1284 | In the Risks/Opportunities module (Project and Program), risks and opportunities can now be arranged in any order by dragging them to the desired position while holding down the SHIFT key and the left mouse button. | |
778 | The titles of the module variants in the Lessons Learned (Cross-Project) module have been updated so that it is clear whether the displayed lessons learned stem from active, inactive, or archived projects. | |
1568 | The header area of the Add Additional Tasks for Time Recording dialog module is now fixed and remains visible at all times when scrolling. | |
Bug Fixes
Key | Description | Server/Client/Web |
|---|---|---|
Project/Portfolio | ||
1139 | Assigning a resource as the person responsible for a risk or opportunity via the Responsible listbox in the corresponding module now works correctly again. | |
1220 | The cause of the Python error message when switching module variants in the Multi-Project Board module has been eliminated. | |
1296 | The cause of the Python error message that occurred when converting an initiative into a project using the From Proposal to Project process model has been eleiminated. | |
1231 | Planning objects that are marked as favorites and have been set to “Archive” will no longer be displayed under Favorites in the user menu. | |
1259 1358 | When you open an employee's employee board from the Department Board panel, the My Planning Objects module now shows the planning objects of the selected employee—rather than those of the logged-in user. | |
1266 | The import of holidays for newly created calendars now works correctly again. | |
1251 | When deactivating or archiving a project, a warning message about external links was displayed, even though there were no longer any external links (only external tasks remained). This issue has been resolved: Now, the message is only displayed if there are actually external links in the project. | |
1247 | The PowerPoint export for grouped data is now working correctly again. | |
1230 | The incorrect display of loads in the With Actual Loads module variant of the Resource Load per Month module has been corrected. | |
1476 1518 | The issues causing Python error messages in the Info Board (Portfolio) module when attempting to filter objective contributions and risk values, as well as when filtering planning objects by objective contribution and risk value without a valid year specified, have been resolved. | |
1504 | In the Time Recording module, users can only select projects for posting hours worked if they have the appropriate access rights, which are determined by the entry in the Object access field. | |
1513 | The resource selection process during resource assignment for tasks involving individual resources (Resources listbox in the Schedule) and multiple resources (Resource Assignment module) has been standardized. Both resource lists now show the same resources based on user permissions. | |
1557 | Die Ursache der Python-Fehlermeldung, die bei der Freigabe eines Prozessmodells mit einem Mastermeilenstein und einem Sammelvorgang auftrat, wurde behoben. | |
1569 | The cause of the Python error message that occurred when clicking on the Show predecessor/successor context menu entry on a newly inserted, not yet saved task in the schedule has been eliminated. | |
DB 26.0.0
Features
Key | Description | Server/Client/Web |
|---|---|---|
General | ||
928 | From now on, a new versioning scheme based on the principle of semantic versioning with three components will be used for PLANTA Project: Major.Minor.Patch. The current software version is 26.0.0.
| |
706 | A new icon | |
961 | Special characters are now permitted in the technical IDs of projects. | |
628 | In the System Information module, exact date and time specifications for the Database parameter are displayed. | |
Project/Portfolio | ||
657 975 | Costs and revenues can now also be posted from the Task module using the corresponding command in the context menu. For this purpose, two dialog modules have been implemented: Cost Posting and Revenue Posting. They are now also used when posting costs and revenues from the schedule. | Web only |
392 | Hyperlinks have been implemented in the planning object and process ID fields in the Non-Postable Objects area in the Time Recording module. | |
641 | The generic tooltip on the traffic light indicating outdated status reports in the Status and Simulations portfolio modules has been converted into a specific one containing precise details of the newer report. | |
849 | Direct dependencies can now also be created between two projects that already have a shared dependency on a third project. | |
796 815 832 806 | Project insights ratings (visualized by a thumb icon) are now also displayed in the Status Report, Project Rating, and Dashboard (Portfolio) modules. | |
740 | A button for copying a direct link (deep link) to the module of the same name has been implemented in the Portfolio Status Report module. | |
677 | The Schedule module now displays an informative dialog message explaining how network cycles can be corrected by adjusting the relationships between activities. | |
1102 | When the schedule is recalculated (e.g., when the main milestone is changed), the system automatically adopts the changed values, so no update is necessary. | |
Risk Management | ||
653 767 1049 | PLANTA now offers the option of generating risks, opportunities, and corresponding measures for a project using AI in the Risks/Opportunities (Project) module. | |
642 643 | In the overview modules containing risk management data, links on the numbers in the rating and traffic light fields provide detailed lists of the risks and opportunities in the corresponding rating category. | |
639 700 620
| In the Risks/Opportunities (Project) and Risks/Opportunities (Program) modules, new data fields have been added for assessing risks (without risk treatment and with risk treatment), opportunities, and monetary damage, and traffic lights have also been added. Links have been implemented in the variants of these modules, which can be used to open risks or opportunities in the corresponding data sheet modules. | |
805 | The Risks and Opportunities (Project) and Risks and Opportunities (Program) report modules display risk data that arises during or after risk treatment by default. | |
617 804 | When a resource is assigned to a risk or opportunity as Person responsible, the corresponding risks and/or opportunities are now displayed in the My Activities module for the respective resource. | |
793 | Risk and opportunity charts in the Portfolio Info Board have been adapted to the new risk management system. | |
681 1047 | The management of risk and opportunity measures is improved by extended status values and grayed-out display of implemented, completed, or rejected risk and opportunity measures. | |
802 | The risk area in the Status (Portfolio) and Portfolio Status Report portfolio modules has been adapted to match the display in projects. | |
801 988 | In the Status (Project) and Status (Program) modules, the display of damage and gross profit values in the Risks/Opportunities subarea has been optimized and traffic light fields for the display of risks and opportunities:have been implemented. In addition, the corresponding data sheet modules can be opened via the links on risks and opportunities. | |
640 799 | Tooltips have been implemented in all modules with risk/opportunity management:
Except for traffic light fields that contain links and matrix chart fields. | |
1059 | If no risk treatment has been performed for a risk yet, the fields “with risk treatment” are pre-filled with the values from fields “without risk treatment,” as these values are initially identical. | |
800 | In the Risks/Opportunities (Portfolio) module, traffic light fields have been implemented to display the recorded risks and opportunities in the sum area, and the matrix display in the Qualitative Assessment area has been optimized. | |
1188 | After updating to the current version, the new Damage extent and Probability of occurrence fields with risk treatment are automatically filled with values from the eponymous without risk treatment fields. The automatically set values apply until they are changed manually. | |
PM Administration | ||
723 | Person Ids can now be changed directly from the Persons module. To do so, select the eponymous context menu command on the record of a person to be directed to the Change Person ID module. | |
987 | Performance for MS-SQL has been improved, and the | |
Bug Fixes
Key | Description | Server/Client/Web |
|---|---|---|
General | ||
809 | If resource requests are disabled, they are no longer displayed when switching between module variants in the My Department module. | |
556 | If several employee boards are opened from the department board and then the Home button is pressed, the system now correctly returns to the department board. | |
691 | If a locked project is accessed in the browser and via a link to time tracking, a correct message is now displayed to notify the user. | |
991 | The | |
727 | Opening the Stakeholder Analysis module from the Other... module without customizer rights in the desktop client is now prevented. The module is only available to normal users in the Web Client. | |
1038 | The cause of the Python error message when attempting to change the existing entry in the New ID field in the Change Person ID module has been fixed. | |
1094 | In the Settings parameter of the Stakeholder Analysis, all traffic lights for the values positive (green), neutral (gray), and negative (red) are now displayed correctly. | |
Project/Portfolio | ||
555 | The display in the Absence module has been corrected. All days of a month are now displayed in one column. | |
775 | No more Python error message is displayed now when clicking on the Favorites star for projects. | |
904 | Deep links for programs work correctly now. | |
814 | In the Program Core Data module, the tooltip on the Open program link button is now displayed correctly. | |
1061 | Export of projects to Microsoft Project now works correctly. | |
1051 | In the Task module, resources that have been assigned to a task as Person responsible can now add new task document records by clicking on the plus symbol next to the area heading. | |
695 | An informative dialog message is now displayed in the Process Status module explaining why it is not possible to assign a predefined resource to a process step. | |
845 | The dialog message stating that the Subprojects module is currently not supported in the web client is now displayed correctly again. | |
647 | The cause of a Python error message when attempting to create a collection of status reports has been fixed. | |
1096 1050 | In the Task module, buttons for inserting new records are only displayed in the areas for which the current user has the respective write rights. | |
1154 | The cause of the Python error message when distributing the effort for a resource in the Resource Plan module has been fixed. | |
1116 626 | The view in the Time Recording module (unfolded projects or task records) now remains unchanged after new hours worked have been saved, existing hours worked have been rectified, or presence times have been recorded or rectified in the Presence dialog module. | |
526 | The assignment of planning objects to multiple portfolios now works correctly again. | |
859 | The Assign Planning Objects module now only shows planning objects that are not yet included in the portfolio. | |
1048 | Performance improvements in the Portfolio Budget module | |
1079 | Access restriction to portfolios now works correctly according to the selected cost center. | |
Risk Management | ||
679 | The risk and opportunity categories are now multilingual. | |
493 | When opening risk measures from the Week Calendar module, no Python error message is displayed anymore. | |
PM Administration | ||
881 | The cause of an Oracle error during data import via LDAP has now been eliminated. | |