Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Ticket

Linked

Function

Type

Subject

SMC-141

Task

Vac planner awarding save - db transaction per HR

Description

Release notes

Right now there is huge db transaction spanning whole save after vacation awarding. Because of legality it can take up to 10 min (hardcoded timeout of single transaction). I removed transaction. It can result it some hr being saved and some not in case of an error but then awarding can just be ran again. New roster saver doesn't use distributed transactions anyway.

Ticket

Linked

Function

Type

Subject

SMC-140

SP-4582

Task

Increase timeout on Async aspx pages to 10 min

Description

Release notes

Ticket

Linked

Function

Type

Subject

POE-107


RAIDO Earth

Bug

Earth - Schedule Not possible to DEP before STD


Description

Release notes

In the Departure dialog it isn't Not possible to enter add DEP before STD

This has been corrected.


Ticket

Linked

Function

Type

Subject

MT-5652


RAIDO Earth

Bug

No lab in Hr HR Log in Earth


Description

Release notes

Opening Hr Log and finding "No lab" on a bunch of places. Works in Cloud.  Environment Mesa uat 19.10

Problem fixed.


Ticket

Linked

Function

Type

Subject

MT-5610


API

Bug

SetRosterData - Func - Roster Time is not updatedAPI


Description

Release notes

Open SoapUI and use SetRosterData method 1. As example, use this script: {code} Sleipner test SRR106 2020-01-09T01:30:00 WAW OPO TES 0040 0240 {code} Where important part is RosterTime block. 2. Set CI and CO times and run the script. 3. Check the Gantt to see changes applied. Problem is, that when you only update RosterTime, CI and CO are not updated on a leg in Raido. The DB is not updated as well. The only chance CI and CO are updated is when you update RD and CI/CO at the same time. [^bandicam 2020-01-09 12-54-32-997.mp4] On above-attached video you can see that RosterTime is updated with RD only- Roster Time is not updated

API bug with SetRoster fixed.


Ticket

Linked

Function

Type

Subject

MT-5575

SP-4592,SP-4597,SP-4599

Fire (mobile)

Bug

Crew cannot access Fire or Cloudroster


Description

Release notes

Crew cannot access Mobile or Web roster

Corrected bug that in a few cases caused the roster to be unavailable after a return to ramp or diversion on one of the crew members on board.


Ticket

Linked

Function

Type

Subject

MT-5489

SP-4591,SP-4604,SP-4096,SP-4456,SP-4595,SP-4600

RAIDO Cloud (Web)

Bug

PH calculations broken in 19.8.8


Description

Release notes

PH calculations are not performed

Fixed, when saving the PH calculations will be updated.


Ticket

Linked

Function

Type

Subject

MT-5479

SP-1639

Sleipner

Story

US eAPIS change from SOAP to REST web service

...

Description

Release notes

US DHS / CBP has changed web service technology from SOAP to REST. We need to support the new interface. Details in attached PDF.

Ticket

Linked

Function

Type

Subject

MT-5459

RAIDO Earth

Bug

Reinstate-GUI-Flight wasn't moved back before saving

Description

Release notes

Steps to reproduce: [^reinsate.mp4] # Cancel multileg flight # Save # Reinstate first leg Note: the issue was found during regression testing.

REST support to eAPIS added.


Ticket

Linked

Function

Type

Subject

MT-5454


RAIDO Cloud (Web)

Task

Improve Training Log

...

Description

Release notes

We need to make an own a dialog for the training events that are tracked in the training log. Possibility to put name and shortcode on each training event and activate/deactivate. . New, copy, edit, and delete options needed. In the Status pulldown menu we need to have options for Failed, Passed and Incomplete.

there is now a new dialogue for setting up the training event functionality.
It obeys the same user right as the training log.

Image Added


Ticket

Linked

Function

Type

Subject

MT-5383


RAIDO Earth

Bug

Reinstate - GUI - STA time is not shownSchedule


Description

Release notes

Open Schedules Create a leg or pick existing one Cancel it > Save (see that STA time shown)

Reinstate canceled leg > see that STA time is not shown) For example, when reinstating canceled leg in Cloud, STA is shown 

Fixed, STA is now shown.


Ticket

Linked

Function

Type

Subject

MT-5301

MT-5485,

RAIDO Cloud (Web)

Bug

Incorrect Pairing copy of 2 day pairing


Description

Release notes

[^Multiday Incorrect copy pairing error-27-11-2019-03-56-56.mp4] See video clip from 48 seconds 1. Built a 2 day pairing with a just flight legs Sunday 08-Monday 09 Dec, saved 2. Right click and select Copy 3. Untick the option "CopyOnlyInFuture" 4. Tick the Copy function, choose number of weeks 7. Click the 'Run' button New pairings are built "in reverse" Day 1 is Monday, day 2 is Sunday - a 2 day pairing becomes a 7 day pairing  Also tested a 2 days pairing that contained legs and RDY - this worked as expected Also tested 2 day pairing with Hotel activity - not working see MT-5299of 2 day pairing

Issue fixed, 2 day pairing (Sunday/Monday) will now be created for the selected period


Ticket

Linked

Function

Type

Subject

MT-5077


RAIDO Earth

Sub-task

Earth - Cut/Paste Confirmed/Sent booking -> status to Reused unactioned and take new crew name


Description

Release notes

Ticket

Linked

Function

Type

Subject

MT-4990

,SP-4434

Fire

Story

User can logon but cannot load Roster

Description

Release notes

Since the upgrade on Tuesday morning we have a user mkorpova who when logging in the roster attempts to load but never actually loads. The roster icon remains in the menu bar with the progress wheel just constantly spinning. Can someone please investigate why? Many Thanks. Our Raido version is 2.4.7 but I cannot select that below as the option only go up to 2.4.4

Ticket

Linked

Function

Type

Subject

MEXT-1282

Earth

Bug

Error on Save operation #2

Description

Release notes

The error looks different than reported in MEXT-1281 so I am submitting this as a new ticket. Environment - Mesa_UAT 19.9 User: Ruslan Per my best recollection... as I wasn't planning to record all of my steps at that point on Dec 4 I was testing ticket 849 by making changes on crewmember 53448 roster. The crewmember had pairings H21219, H21220, H21221 on the roster. Assigned pairing H21222 and applied LE ZS to the first leg. Clicked Save. Received the unexpected error captured in the screenshot below. Expectation: no error. I haven't attempted to recreate the observed behavior. Logs attached. 

Cut/paste HTL booking is not kept for the new crew member

This has been corrected.


Ticket

Linked

Function

Type

Subject

MEXT-663

MT-5147

Fire

Task

Training Concept Fire- Instructors need to see trainee details

Description

Release notes

I would like the following information available in Fire: 1) The following items should ONLY be available to the instructors that are listed for the training event - Student Names - Student Employee Numbers - Student Phone Numbers - Training Statues for each student (this is the lessons) - Any notes the schedulers adds to the training event 2) The following items should ONLY be available to the students that are coming in for training, for their training session - Partner Name - Partner Employee Number - Training Statues for only themselves - Instructor Name

It is now posssible to view training sessions in Fire

Ticket

Linked

Function

Type

Subject

AUA-6

SP-1291,SP-1151,MT-5688


StoryRights

are being too restrictiveuser rights


Description

Release notes

We have an issue with user rights and group affiliations . As an example I created a user Henrik in aua-test with the normal support password, affiliated to Administrators and LNZ. This will restrict me from producing an Overview Roster report for crew based in INN, as the usergroup LNZ have a restriction to the report, as shown below  Normally, the least restrictive should be adhered to. This needs to be fixed soon.being too restrictive. 

There is now a possibility to defined priority for a user group. The highest priority is 1.
The user right from the user group with the highest priority is the one assigned to a user.
priority is calculated according to the following rules:

Group is admin and has defined priority
Group is admin but has not defined priority → then priority is calcualted according to created date time (the older group has higher priority)
Group is not admin and has defined priority
Group is not admin but has not defined priority → then priority is calcualted according to created date time (the older group has higher priority)

Image Added