2.1.16 31OCT18
Ticket | Linked | Function | Type | Subject |
MT-1380 | RAIDO Cloud (Web) | Task | Log page accessible without credentials |
Description | Release notes |
Server log in Raido Cloud (Web) is accessible without valid user credentials. | Access to log page is now only available only for administrators. |
Ticket | Linked | Function | Type | Subject |
MT-1570 | MT-1487 | Bug | Date bug in Ad-hoc edit dialog for multi leg scheduled flights. |
Description | Release notes |
Multi leg schedules where the first leg is past midnight shows the wrong date on the second leg. | This has been fixed. |
Ticket | Linked | Function | Type | Subject |
MT-1929 | Story | operating passenger terminal indicator in RAIDO. |
Description | Release notes |
Enable import of passenger terminal indicators from the SSIM file. | Raido can now read terminal information when importing a SSIM file. |
Ticket | Linked | Function | Type | Subject |
MT-2288 | Bug | Adhoc edit picks wrong day when using the schedule gantt in local time mode. |
Description | Release notes |
When a flight operates over midnight in UTC, but the gantt is set to local time (UTC+). Ad-hoc edit will assign incorrect dates when splitting the schedule. | Ad-hoc edit will no longer pick the incorrect date when making a change, When the schedule gantt time reference is set to a different timezone. |
Ticket | Linked | Function | Type | Subject |
MT-2236 | RAIDO Cloud (Web) | Bug | The slot is already confirmed after changes |
Description | Release notes |
1. Create scheduled flight AAA-BBB-CCC. 2. Confirm the slots (K). 3. Adhoc edit AAA and change the flight number for BBB, slots show as already confirmed with the new flight number. 1. Adhoc AAA-BBB and return leg BBB-AAA. 2. Confirm the slots (K) for both. 3. Adhoc Edit AAA and change the flight number, slots show up as confirmed. it's the same when you edit the return. | Fixed an issue that resulted in corrupt slot conversation history, when changing the flight id in Ad Hoc Edit. |
Ticket | Linked | Function | Type | Subject |
MT-2235 | Bug | Slot message is not generated for arrival station when flight is over midnight. |
Description | Release notes |
1. Create a flight AAA-BBB (flight is over midnight) 2. Confirm the slots (K) 3. Ad-hoc Edit the flight and change the flight number. 4. Then cancel it, SCR for BBB is not generated. | Fixed problem with messages for arrival slot not being generated for overnight legs, when the leg has had a flight id change. |
Ticket | Linked | Function | Type | Subject |
MT-2216 | MT-2243, MT-2228, | Bug | The issue with slots when rerouting |
Description | Release notes |
1. Create multi-leg flight AAA-BBB-CCC 2. Confirm all slots (K) 3. Remove the last leg (BBB-CCC) using Ad-hoc Edit, 4. Reset to second step, but this time remove the second leg using cancel/delete in the context menu instead. Both step three and four should give the same result. However the slot messages in example three are incorrect for AAA and CCC , and BBB and CCC in example four. | Ad-hoc edit now generates a correct slot delete message(s) when removing routing, and C/R for remaining legs. |
Ticket | Linked | Function | Type | Subject |
MT-2204 | Bug | Service Level Agreements - Saving issue modifying Station not possible after initial save |
Description | Release notes |
It's not possible to modify the station on any existing Service Level Agreement | Issue with saving SLA when station is changed has been fixed. |
Ticket | Linked | Function | Type | Subject |
MT-2202 | RAIDO Earth | Bug | Service Level Agreements - Saving issue after deleting row out of SLA |
Description | Release notes |
Saving issue occurs when:
| SLA saving has been fixed. |
Ticket | Linked | Function | Type | Subject |
MT-2185 | Sleipner | Story | Rotation File via Sleipner |
Description | Release notes |
Issues with Importing rotation file via Sleipner, for example updating aircraft registrations. | Several Sleipner rotation file issues has been fixed, importing a rotation file to update the aircraft registrations now works, with or without hyphen |
Ticket | Linked | Function | Type | Subject |
MT-2141 | MT-2235, MT-2236 | Bug | Canceling a schedule with a pending C/R. |
Description | Release notes |
1. Create a flight. | Cancelling a flight caused a crash if the flight flight Id changed and the slot change was not confirmed back by the coordinator, this is now fixed. |
Ticket | Linked | Function | Type | Subject |
MT-1676 | Bug | The last leg of a changed schedule points to a different period. |
Description | Release notes |
Issue occurs to a multi leg flight schedule (AAA-BBB-CCC) with confirmed slot, when the first leg has an arrival after midnight on the last day of the season. If changing 'ValidTo' and 'ValidFrom' on the scheduleto a shorter time span within the same season, this would cause the last leg of the schedule to point to the wrong season and the wrong stations would be shown if rerouting the shortened schedule to AAA-CCC. | The last leg of the schedule is now pointing to the correct period, and the stations will be correct when rerouted. |
Ticket | Linked | Function | Type | Subject |
MT-1551 | RAIDO Cloud (Web) | Bug | Creating schedule in local time. |
Description | Release notes |
UTC/Local Time selector has no function when creating a schedule.
| The drop down is disabled and fixed to UTC. |
Ticket | Linked | Function | Type | Subject |
MT-1018 | SP-1058, MT-1752, | Story | RU Visa document type warnings |
Description | Release notes |
Visa HR document does not show a missing document warning when the valid from date is forward in time from the activity it should warn for. | The approach to defining the document's validity has changed. Raido now checks the 'Expiry Date' and 'Valid From' properties in the document setup, but the 'ValidTo' Property in the setup is only accounted for if there are no existing transactions added. Then it checks the active and all the historical transactions (if any exists) to find out whether their 'ValidFrom' and 'Expiry Date' date interval overlaps with the activity's time index (usually activity start time/date). If the 'Expiry Date' is not set on the transaction, the document will be considered valid perpetually |
. And if 'ValidFrom' is not set on the oldest or the only existing transaction it will be considered valid from the beginning of time. The 'Active' and 'Default' check boxes in each transaction have no function and will be removed in version 2.2. |
Ticket | Linked | Function | Type | Subject |
MT-2321 | Other | Story | Timzone update 2018g |
Description | Release notes |
Add support for latest Timzone update, 2018g | 2018f & 2018g updates added. 2018g Morocco switches to permanent +01 on 2018-10-27. 2018f Volgograd moves from +03 to +04 on 2018-10-28. Fiji ends DST 2019-01-13, not 2019-01-20. Most of Chile changes DST dates, effective 2019-04-06. |
Ticket | Linked | Function | Type | Subject |
MT-2316 | RAIDO Earth | Bug | Suffix not supported when importing ASM/SSM messages. |
Description | Release notes |
Importing an ASM or SSM message containing a suffix it will cause an error. | ASM/SSM import now handles suffix in the messages. |
Ticket | Linked | Function | Type | Subject |
MT-2298 | MT-1929 | RAIDO Cloud (Web) | Bug | SSIM import does not support terminals with two characters. |
Description | Release notes |
When importing a SSIM file that contain terminals with 2 characters it will only parse the first letter and then report that it's missing. | Importing SSIM files with 2 letter terminals is now working. |
Ticket | Linked | Function | Type | Subject |
MT-2205 | RAIDO Earth | Bug | Change text on buttons in ground wizard. |
Description | Release notes |
The buttons when uploading historical data are pointing to the opposite function
| Demands - upload historical and forecast data - incorrect text on buttons has been fixed. |
Ticket | Linked | Function | Type | Subject |
MT-2053 | SP-2567, SP-2872 | Bug | Document functionality |
Description | Release notes |
The document functionality has become broken with the introduction of a check against the Valid from date in transactions. This creates issues with erroneous warnings, as legality only checks the last transaction. | The approach to defining the document's validity has changed. Raido now checks the 'Expiry Date' and 'Valid From' properties in the document setup, but the 'ValidTo' Property in the setup is only accounted for if there are no existing transactions added. Then it checks the active and all the historical transactions (if any exists) to find out whether their 'ValidFrom' and 'Expiry Date' date interval overlaps with the activity's time index (usually activity start time/date). If the 'Expiry Date' is not set on the transaction, the document will be considered valid perpetually |
. And if 'ValidFrom' is not set on the oldest or the only existing transaction it will be considered valid from the beginning of time. The 'Active' and 'Default' check boxes in each transaction have no function and will be removed in version 2.2. |
2.1.15 01OCT18
Ticket | Linked | Function | Type | Subject |
MT-2181 | RAIDO Web (Cloud) | Task | Wrong reference date on vacation bids. |
...