Mithali Raj Considering Retirement After Being Dropped From Semi Finals of the ICC T20 Women’s World Cup 2018?
Mithali Raj (Photo Credits: Twitter)

Mithali Raj was dropped from the semi-final match between India and England last week during the ICC T20 Women’s World Cup 2018. The decision came in as a surprise for the fans particularly because Mithali had won a couple of Player of the Match awards during the mega-event with half-centuries. But the team for the semi-finals wanted to retain the winning combination. Now, this surely did not go down well with the former Indian captain and as per reports, Mithali is planning to retire from the T20I format. Mithali, Harmanpreet Meet CEO Johri, GM Karim Separately, Powar Summoned on Wednesday.

A source told Mid-Day, “She struggled to sleep peacefully throughout the tournament because there was a lot of uncertainty surrounding her place in the team. There was no clarity over her role in the team and her batting position. She was told about her omission from the semi-final after the warm-up session on match day.” Mithali missed a league game against Australia due to an injury but was all set to make a comeback for the semis. But she was not included in the squad.

India crashed out of the tournament as they were defeated brutally by the Brits by 8 wickets. Mithali Raj’s manager Aanisha Gupta also slammed the captain of the woman’s cricket team Harmanpreeet Kaur. She went on to label Kaur as ‘manipulative, lying, immature and undeserving captain’. “Unfortunately, the Indian women’s cricket team believes in politics not sport. After witnessing what Mithali Raj’s experience could do in India vs Ireland, it’s shocking that they went with what pleases Harmanpreet Kaur – a manipulative, lying, immature, undeserving captain,” she tweeted. However, the tweets were deleted later.

Now as per the latest news, Mithali Raj and Harmanpreeet Kaur met BCCI CEO Rahul Johri after suffering a humiliating defeat. The BCCI has also sent a summons to coach Ramesh Powar for a meeting regarding the same issue.