|
| 1 | +--- |
| 2 | +author: meshcloud |
| 3 | +title: Release 2025.2.0 |
| 4 | +--- |
| 5 | + |
| 6 | +Release period: 2025-01-08 to 2025-01-15 |
| 7 | + |
| 8 | +This release includes the following issues: |
| 9 | +* Finalize Partly Incomplete Chargeback Statements |
| 10 | +* Fixed Chargeback Line Item Numbering |
| 11 | +* No notifications for deleted API Keys |
| 12 | +* Projects without Payment Methods for Chargeback 2.0 |
| 13 | +* Product Search in Tenant Usage Reports |
| 14 | +* Move disabled platforms down platform selection |
| 15 | +* Fixes Upgrade of Building Blocks with Dependency |
| 16 | +<!--truncate--> |
| 17 | + |
| 18 | +## Ticket Details |
| 19 | +### Finalize Partly Incomplete Chargeback Statements |
| 20 | +**Audience:** User<br> |
| 21 | + |
| 22 | +#### Description |
| 23 | +Previously, in the new chargeback 2.0 process, non-finalized chargeback |
| 24 | +statements from past periods were automatically deleted. This could happen if |
| 25 | +a single Tenant Usage Report that was part of this chargeback statement was |
| 26 | +not finalized, for example, because the underlying platform was already |
| 27 | +deleted and therefore no new costs were collected. This has been fixed now. |
| 28 | +If a Tenant Usage Report cannot be finalized for whatever reason, the |
| 29 | +associated chargeback statement will be finalized and it will have this |
| 30 | +particular Tenant Usage Report removed from its line items. This fix also |
| 31 | +creates missing chargeback statements that were deleted in the past, because |
| 32 | +some usage reports were not finalized. |
| 33 | + |
| 34 | +### Fixed Chargeback Line Item Numbering |
| 35 | +**Audience:** Partner<br> |
| 36 | + |
| 37 | +#### Description |
| 38 | +The tenant usage reports in chargeback statements previously displayed |
| 39 | +incorrect numbering. Additionally, these reports were duplicated when |
| 40 | +multiple line items existed for them with different sellers. Both |
| 41 | +issues have now been resolved. |
| 42 | + |
| 43 | +### No notifications for deleted API Keys |
| 44 | +**Audience:** User<br> |
| 45 | + |
| 46 | +#### Description |
| 47 | +Notifications are no longer sent out for API keys |
| 48 | +that are about to expire in case the API key has been |
| 49 | +already deleted. |
| 50 | + |
| 51 | +### Projects without Payment Methods for Chargeback 2.0 |
| 52 | +**Audience:** Customer, Partner<br> |
| 53 | + |
| 54 | +#### Description |
| 55 | +With this change and Chargeback 2.0 activated, if your project doesn't have a payment method because the previous |
| 56 | +one expired and you haven't set a new one yet, we'll still generate and finalize tenant usage reports without |
| 57 | +payment methods, but chargeback statements won't be generated. |
| 58 | +When you set a new payment method, all past tenant usage reports that were missing one and include |
| 59 | +the new payment method get updated. Also chargeback statements for those periods get generated with the new |
| 60 | +payment method. |
| 61 | + |
| 62 | +### Product Search in Tenant Usage Reports |
| 63 | +**Audience:** User<br> |
| 64 | + |
| 65 | +#### Description |
| 66 | +As part of improving the user experience in the financial overview, a search bar has been introduced to the Product column in the Tenant Usage |
| 67 | +Report, allowing you to quickly search and filter resources by product, eliminating the need to navigate through extensive cost lists manually. |
| 68 | + |
| 69 | +### Move disabled platforms down platform selection |
| 70 | +**Audience:** User<br> |
| 71 | + |
| 72 | +#### Description |
| 73 | +When selecting platforms, either for an existing or new project, all disabled platforms are moved to the bottom of the list. |
| 74 | +This should make it easier for users in meshStacks with a lot of platform to filter out platforms that are not available |
| 75 | +either due to mismatching policies or platform misconfiguration. |
| 76 | + |
| 77 | +### Fixes Upgrade of Building Blocks with Dependency |
| 78 | +**Audience:** Partner<br> |
| 79 | + |
| 80 | +#### Description |
| 81 | +This fixes a bug that prevented upgrading an existing building |
| 82 | +block to a new version in which the parent dependency was removed. |
| 83 | + |
0 commit comments