2.1.18 19DEC18
Ticket | Linked | Function | Type | Subject |
MT-2541 | Task | Add logs for SSIM import |
Description | Release notes |
We are not sure if the users are selecting the right dates and filter when using the SSIM import. Please add a log that records what filter and period was used, together with what user performed the import. | There is now a log that records the data when the SSIM import wizard is used. |
Ticket | Linked | Function | Type | Subject |
MT-2540 | Bug | Removing SGrid for all users |
Description | Release notes |
SGrid needs to be removed since it is no longer supported. | SGrid has been removed. |
Ticket | Linked | Function | Type | Subject |
MT-2527 | RAIDO Cloud (Web) | Bug | RAD Numbering is not correct |
Description | Release notes |
After the ADM has been sent for a day, then each change to tail assignments should generate a RAD message indicating the new assignment for that aircraft. Two issues has come up 1. A cancellation generates a RAD, but still keeps NR01 in the message causing confusion. 2. A new flight does not generate a RAD. | RAD sequence numbers for cancellations and new flights has been corrected. |
Ticket | Linked | Function | Type | Subject |
MT-2526 | RAIDO Earth | Bug | SSM NEW import not working correct |
Description | Release notes |
When importing SSM NEW messages, some of the messages where moved to the 'Removed Message' Tab in the import wizard. Causing them to not get imported. | Import issue has been corrected. SSM NEW messages will no longer be added to the 'Removed Message' Tab in the wizard. |
Ticket | Linked | Function | Type | Subject |
MT-2491 | Bug | Day Notes are not shown properly |
Description | Release notes |
Sometimes 'Day Notes' are not visible for some roster gantt users. But it works fine when logged in as an administrator. However they show up for everyone in the list of existing notes inside the note dialog. The issue is with the flag and preview in the gantt. | GUI issue with drawing note flags in the gantt has been corrected. |
Ticket | Linked | Function | Type | Subject |
MT-2415 | RAIDO Cloud (Web) | Bug | unactioned roster |
Description | Release notes |
Our crew members are able to see unsaved roster changes by printing the 'My Roster' report. | Unsaved roster changes are no longer displayed in the 'My Roster' report. |
Ticket | Linked | Function | Type | Subject |
MT-2122 | SP-2778 | Story | Flights outside of SSIM-range deleted on import |
Description | Release notes |
The SSIM import needs to warn if there are activities outside the schedule period(s) | Added check to verify system data to avoid mismatch issues with import, like when activities are outside the correct period. |
2.1.17 29NOV18
Ticket | Linked | Function | Type | Subject |
MT-2389 | RAIDO Cloud (Web) | Bug | Incorrect estimated landing time |
Description | Release notes |
| The MVT estimated landing time is not correctly added, and a incorrect +1 day difference is added. This only affects the landing/touchdown time. | Fixed incorrect Estimated Touch Down time calculation for MVT message. |
Ticket | Linked | Function | Type | Subject |
MT-2383 | RAIDO Cloud (Web) | Task | AutoRostering - save daily values for each hr and reuse them in legality checks |
Description | Release notes |
Auto-rostering performance impact due to excessive legality re-calculation, daily values should be saved for each HR after the initial load. | Performance improvements introduced in auto-rostering when checking legalities. |
2.1.16 31OCT18
...
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. |
...
| Ticket | Linked | Function | Type | Subject |
MT-1903 | MT-1889 | Bug | Schedule Edit split frequency, makes the activities move a day forward |
Description | Release notes |
Schedule Edit split frequency, makes the activities move a day forward | 1. Create schedule with frequency 12345 2. Edit the schedule change frequency to 12 and press new period 3. Change the suffix to D next and save (the activities will not move one day any more) |
Ticket | Linked | Function | Type | Subject |
MT-1892 | MT-1889 | Bug | In Schedule edit, Load season button will bring back Reduce and Expand buttons |
Description | Release notes |
If user press load season button the reduce and expand buttons will be visible again while they should be hidden in any case. | Even with pressing the load season, the reduce and expand buttons will not appear anymore and the next button was available too after load season but is now disabled. |
Ticket | Linked | Function | Type | Subject |
MT-1889 | Bug | Schedule Edit>Wrong period and frequency |
Description | Release notes |
Create a flight with frequency 12345 from 21may18 to 31jul18. Schedule Edit Change frequency to 12 and add suffix R. Refresh button and then click new period (as it blocked without it). Save. I expected to change Suffix only on the flights with frequency 12, but it has been added to all flights. | There frequency split is fixed. |
Ticket | Linked | Function | Type | Subject |
MT-1880 | RAIDO Cloud (Web) | Bug | After adding new period, only one period exists, frequency is not changed |
Description | Release notes |
After creating a new period (26march-17oct), adding sat and sun (so it covers the full week), the flight is not added to the Gantt (sat,sun). Also, the period is not broken into two periods. An existing flight in a later period (22ndOCT) shows a new period to which it doesnt correspond. | The user can no longer add frequency to a schedule by new period. |
Ticket | Linked | Function | Type | Subject |
MT-1873 | SP-2044, SP-2134 | RAIDO Cloud (Web) | Bug | Missing Euro control ready state on FPL causes error. |
Description | Release notes |
FPL from Eurocontrol may contain Ready State 3 - In Raido we only have 0 = unknown, 1 = Ready, 2 = Not ready. We can't parse the value since we don´t have ready state value 3. This will in turn cause an error when trying to add MTV times in 'Activity Info'. Please add Ready State with '3 =' as an option to make it possible to parse the messages. | Added 3 as an option to prevent the crash |
Ticket | Linked | Function | Type | Subject |
MT-1445 | Bug | New Period functionality works Incorrectly in Schedule Edit Dialogue |
Description
Release notes
Resolved by MT-1889 |
Ticket | Linked | Function | Type | Subject |
MT-809 | SP-304 | Story | Dynamic leg report. Unique ID |
Description | Release notes |
Can we add an additional parameter to Dynamic Leg Report which would be the Id number? | ID field can now be added as a column in every dynamic report |
2.1.4 22MAY18
...