April 29, 2017 12:07 am
Updated: April 29, 2017 12:12 am

#SajjanBattles mocks defence minister for inflating his role fighting the Taliban

Questions are being raised about Canada's defence minister after he was caught inflating his role on the battlefield. In a speech, Harjit Sajjan claimed to be the "architect" of a major offensive against the Taliban. But as David Akin explains, he wasn't.


Twitter users unleashed a round of mockery at Harjit Sajjan on Friday after the defence minister expressed “regret” for inflating his role in a 2006 offensive against the Taliban in a Friday statement.

Earlier this week, Sajjan said he was the “architect” of Operation Medusa, an offensive in Afghanistan that has been recognized as the biggest combat operation Canada mounted since the Korean War.

Sajjan played an intelligence role in Afghanistan, but he later clarified that he wasn’t the architect behind Medusa.

“My comments were in no way intended to diminish the role that my fellow soldiers and my superiors played in Operation Medusa. I regret that I didn’t say this then, but I want to do so now.”

That statement did nothing to stem a flood of cheeky tweets from emerging under the hashtag #SajjanBattles, however.

Conservative MP Erin O’Toole kicked things off by “thanking” Sajjan for his Second World War exploits.

Twitter users quickly followed suit by jokingly placing the defence minister in various historic battles.

Users also placed him in fictional ones such as Helm’s Deep in The Lord of the Rings: The Two Towers.

Twitter user Matthew Clancy put Sajjan at the Battle of Endor in Star Wars: Episode VI – Return of the Jedi.

MP James Bezan put him in “Rogue One.”

This user put him in the final battle of Saving Private Ryan.

And in a hockey fight in the movie Slap Shot.

Twitter user Ben Silverman put Sajjan in the War of 1812.

And user Ettore placed the defence minister in the Battle of Gondor from The Lord of the Rings: The Return of the King.

© 2017 Global News, a division of Corus Entertainment Inc.

Report an error


Want to discuss? Please read our Commenting Policy first.