Jordan Shua's Troubled History Continues at Beitar Jerusalem

Beitar Jerusalem player Jordan Shua has once again found himself in trouble, adding to his well-documented history of off-field incidents. This latest event, which reportedly involved problematic social media posts, has led to the club needing to address another internal crisis. As is tradition, the club's management, including figures like Barak Abramov and Kfir Edri, are opting for behind-the-scenes discussions with Shua and his agent, rather than immediate disciplinary action.

While coach Almog Cohen's decision to not start Shua in a recent match is mentioned, the article emphasizes that Shua's recurring issues are the primary concern. The piece suggests that multiple coaches and management figures have faced similar situations with Shua, indicating a pattern that extends beyond any single individual. The author posits that if one professional struggles with a player, they might be at fault, but when multiple professionals encounter the same problem, the player's behavior is the consistent factor.

Despite his problematic record, Shua is considered important to Beitar Jerusalem's success, with aspirations for titles and a potential move abroad. However, his "Google record" is consistently cited as a major obstacle to securing a lucrative contract overseas. The latest incident has reportedly added ten negative items to his online profile, suggesting a persistent pattern of self-sabotage.

The article concludes that while Shua is not a bad person and often regains composure, the club must break this cycle of recurring incidents. Beitar Jerusalem, now a legitimate club with a strong fanbase, needs to evolve beyond tolerating such behavior and establish firmer principles. It is expected that Shua will return to the starting lineup within a game or two, but the club's long-term strategy must address these recurring issues.