PTI opposes Operation Azm-e-Istehkam in K-P jirga

Jirga also calls for former premier Imran Khan's release


News Desk June 26, 2024
PTI officials during a jirga in Khyber Pakhtunkhwa on June 26, 2024. Photo: Express

The Pakistan Tehreek-e-Insaf (PTI) officially opposed Operation Azm-e-Istehkam during a tribal jirga in Khyber-Pakhtunkhwa (K-P) on Wednesday. It also passed a resolution calling for the release of Imran Khan from jail.

According to Express News, PTI organised a jirga to deliberate on Operation Azm-e-Istehkam, attended by elders and dignitaries from various tribes in K-P.

The central and provincial leadership of PTI were present on the occasion and speeches were made by various leaders, including head of the Tehreek Tahaffuz-e- Ain-e-Pakistan (TTAP) Mahmood Khan Achakzai.

Key resolutions passed

The jirga approved a resolution addressing barriers to trade with Afghanistan and ongoing negotiations at the Pakistan-Afghanistan border. Another resolution opposing Operation Azm-e-Istehkam was presented, with participants demanding that the matter be debated in the national and provincial assemblies, involving all stakeholders.

Also Read: K-P govt withholds support for Operation Azm-e-Istehkam

Additionally, a resolution calling for the release of PTI leaders and workers, including the party's founding chairman, who they claimed have been detained on political charges, was approved while another resolution recognising the local population's rights to natural resources was also passed by a show of hands.

Resolutions passed by majority vote

Several resolutions were presented at the jirga, all of which were approved by majority vote. K-P Information Advisor Barrister Saif stated that the approved resolutions would be presented in the provincial assembly and the council.

The chief minister will present the approved resolutions in the provincial assembly for further approval, he added.

COMMENTS

Replying to X

Comments are moderated and generally will be posted if they are on-topic and not abusive.

For more information, please see our Comments FAQ