Has anyone ever had a problem with their oneworld ticket while using that ticket?

I'm currently on a DONE3. Sitting at HEL for HEL-LHR. Booking on AY with an MH code. When attempting to check in, that sector, and only that sector presented problems. They couldn't find it under the normal ways of looking up tickets (name, passport, PNR) and could only find it when imputing the full ticket number. It took almost an hour and 5 different agents to get it worked out.

It seems that MH cancelled the sector and it was showing to AY as waitlisted.

I've had some other problems in the past, but those have been a result of a clueless agent changing something they shouldn't have when making changes to other flights or connecting across tickets.

Was it a connecting flight from HEL-LHR-KUL or was it just booked as one off sector.. cos if you just booked HEL-LHR without connecting onto KUL, MH will cancel the flight cos that's what codeshares are for.

You should have just booked on AY since its their metal in any case. That's the misunderstanding with a lot of codeshared flighhts especially on OW. People think that one may just book say AA codeshares within Asia on CX to get full miles in economy. But without a connecting flight across the transpacific, the booking will evetually cancel - if one can even book it in the first place.

There is no such thing as a OW ticket. The ticket had to have been issued by one carrier which presumably is a member of OW. Same with the HEL-LHR. There is an operating carrier. Could be others codesharing, but there's only one operating carrier.

As others note, if you are flying on an AY-operated flight using another carrier's codeshare for a single segment, it makes no sense and I'm surprised you were able to book it.

In any event, no matter what you think you hold, I would always confirm that the operating carrier shows you with positive confirmed space. Here, AY would have told you of the problem well in advance and it could hopefully have been repaired.

I assume he means a oneworld explorer ticket.

Who issued the ticket? They and their computers should have known whether the code-share was legal or not. If you look up the MH codeshare flight number on EF or a similar tool and look at the rules it should clearly state that. (Not that knowing that the ticketing carrier screwed up is going to do much good in this case, although if they did and left you in a tight spot they should do whatever it takes to solve your/their problem.)

And what does the poster mean who says 'that's what code shares are for'? I was pretty sure that code shares were a marketing tool that a carrier could use however they saw fit, including perhaps an unmarried segment between two cities.

More generally re flight-watching: these days there are more inexperienced airline agents, more complicated rules, computers talking to other airlines' computers using disparate data bases and perhaps buggy code, and bankrupt airlines with no room in the budget to care much more about their pax than legally required. It is alas prudent to keep watch on all your forward bookings lest you receive surprising news at OLCI or the airport desk.

The ticket number is the golden one, although PNRs (cross-referenced to the operating carrier when necessary) are usually handy. A copy of the rules for your flights can also be handy in the case an agent is dead wrong - quoting the text will often let reason reign.

It's a DONE3 oneworld explorer issued by CX. That flight was on AY and booked under the MH code. It was showing as just fine on every airlines booking system until that morning when I arrived to check in. AY couldn't work out what happened to it, but they removed the MH sector and rebooked it with the AY code.