Martyn Houghton Posted November 12, 2019 Posted November 12, 2019 I am attempting add a Label to a JIRA Issue using the JIRA Cloud 'update Issue' integration node. I am passing the mandatory key field and a value in the Labels attribute, but the update is not adding the label to the issue. I tested this with both the injections for the values from variables as well as hard coding as below. I am wondering if the Labels element which is a new addition is using the wrong attribute type/dialog, as it is different to the way you set 'Labels' when creating the case using the 'Create Issue' option. Cheers Martyn
Steve G Posted November 12, 2019 Posted November 12, 2019 Hi @Martyn Houghton, I've fixed the issue with the Update Issue labels. The UI needed to be a little different to the Create Issue one, as we needed to specify if you were adding new labels, or removing existing ones: Let me know how you get on with this. Cheers, Steve
Martyn Houghton Posted November 14, 2019 Author Posted November 14, 2019 @Steve G I have tested the new form and the node does not error and the logic follows the automation success outcome, but the label does not get appended in JIRA. As there is now parameter returned I not able to debug why or what it thinks it has done. Cheers Martyn
Steve G Posted November 14, 2019 Posted November 14, 2019 Hi @Martyn Houghton, I've not been able to replicate this issue When I create a new issue from a request via a workflow, and then update the labels on the issue with a string followed by an injected parameter (request reference, as per your example), the labels on the new issue get updated as expected. See below - the BPM on the right shows how I'm updating the labels. The Update Jira Issue node is removing a label that I created in the Create Issue node, and adding a new one with the request reference tagged on to the end of my instance URL. And the updated issue in my Jira instance showing the updated labels: I've added a status output parameter to the operation so you can use a decision node to catch when this operation fails on your Jira instance though, and have added some extra logging so we can hopefully see why this is failing. Give it 10 mins to hit your instance before you do any more testing, then let me know once you're done and I'll have a look at the logs. Cheers, Steve
Martyn Houghton Posted November 14, 2019 Author Posted November 14, 2019 @Steve G I notice you are passing the project value as well as the key and the labels. Does it work for you if you remove the optional project parameter? I will give it a test with the new version. Cheers Martyn
Steve G Posted November 14, 2019 Posted November 14, 2019 Hi @Martyn Houghton, Yes, it still works with that removed. Cheers, Steve
Martyn Houghton Posted November 18, 2019 Author Posted November 18, 2019 @Steve G Now getting the following error now when attempting to update the label. Cheers Martyn
Steve G Posted November 18, 2019 Posted November 18, 2019 Hi @Martyn Houghton, This is usually a config or rights issue on the Jira instance - specifically the user account making the API calls not having access to add/edit labels on issues... More information can be found in this post on the Atlassian Community: https://community.atlassian.com/t5/Jira-questions/Problem-trying-to-add-label-using-cURL/qaq-p/255420 Cheers, Steve
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now