I’m trying to figure out how to add labels to JIRA tickets when I create them or update existing ones using the SOAP API. I’ve looked through the WSDL file but couldn’t find anything related to labels when I searched for that term. Even when I retrieve a ticket that I know has labels assigned to it, the API response doesn’t show any label information. Has anyone managed to work with ticket labels through the SOAP interface? I’m wondering if there’s a specific method or field I’m missing, or if labels might be handled differently in the SOAP API compared to other interfaces.
totally agree! the SOAP API’s handling of labels is a pain. you’re right about the WSDL - no label fields there. migrating to REST sounds like your best bet, or maybe use custom fields for labels if it’s feasible. good luck!
The JIRA SOAP API has major limitations with labels. From my experience with older JIRA versions, labels weren’t fully exposed through SOAP - that’s why you can’t see them in the WSDL or API responses. It was a known gap in their SOAP implementation. Labels were mainly available through REST API or the web interface. If you’re stuck with SOAP, try a hybrid approach - use SOAP for basic ticket stuff and make separate REST calls for label management. But honestly, I’d recommend switching to REST API completely if you can. Atlassian deprecated SOAP years ago and it doesn’t support many newer JIRA features, including proper label handling.
Been there with legacy systems forcing deprecated APIs. SOAP’s label limitation is brutal.
Skip the workarounds and custom REST wrappers - just automate it. Set up a workflow that watches your SOAP ticket operations and handles label updates via REST calls automatically.
I’ve fixed similar API version nightmares by building automated bridges. The workflow catches SOAP ticket creation, grabs the info, then fires off REST calls to add labels. No messy manual hybrid stuff.
You can get creative - parse ticket descriptions for keywords and auto-assign labels, sync between systems, or batch process during off-hours.
Best part? Your existing SOAP integration stays untouched. Layer the automation on top and it handles labels seamlessly.
This API bridging approach beats building custom solutions from scratch every time.
Had this exact problem two years ago on a legacy integration. The SOAP API just doesn’t do labels as they weren’t around when it was built. I ended up using custom fields as a workaround, but it comes with drawbacks like losing auto-completion and filtering. I also attempted to parse ticket descriptions for hashtags and create a scheduled script to add labels through REST. The bottom line is that the SOAP API is outdated and doesn’t support newer JIRA features. If switching to REST isn’t an option yet, consider building a REST wrapper service to manage labels while continuing to use SOAP for other functions.