Paul Lemon

Ah sorry - missed that too! :) This must be an issue with Jest / Node on your machine. I'm sure its a bug but not one I can fix...

using `npm test` will run all tests - does that have the same issue? `npx jest --coverage` runs all tests and generates a coverage report to help you see gaps...

I can't reproduce this. This is the schema for the custom field in our Server side JIRA for labels ``` {schema={custom=com.atlassian.jira.plugin.system.customfieldtypes:labels, type=array, items=string, customId=17094 }, navigable=true, orderable=true, custom=true, name=Projects Affected,...

Could you share the schema from your server instance? Could you find the payload in the logging as well?

Thanks for this - I will test.

I can reproduce locally and will work on this later this evening.

It only occurs when using a custom "label" field rather than the built in Jira Label field.

Should have a fix soon - shall I start 1.2.1 branch for fixes?

+1

The use of basic auth and storage of those credentials needs improvement. OAUTH looks like a better option https://developer.atlassian.com/server/jira/platform/oauth/ Worth an investigation to see if it's feasible and what impact...