@biakymet Could you take a look please

Cosmetic: erroneous whitespace?

:+1:

Custom field id may be different in other versions, for example in testing stage JIRA this field has id customfield_13200, so, please, use request for finding right id. https://confluence.atlassian.com/jirakb/how-to-find-id-for-custom-field-s-744522503.html

I've checked the prod JIRA and it uses customfield_12811. If you inspect element on a JIRA issue, on QA contact you can see the value of the custom field.

Yes, but again, different JIRA use different ids, stage JIRA use id customfield_13200, so it will be better to not hard code id.

Hmm but if we don't hard code it in, then we don't need this PR and if people want to add custom fields they can use the custom_fields array that is already supported? What were you thinking instead?

My point is, this field is used a lot, so it will be better to add support in configuration not by id, but by name. In that case it's not needed to looking for id and this will improve user experience.

That was what I was thinking as well. But if we want that; we will need to hard code the custom field ID into the program, no?

That was what I was thinking as well. But if we want that; we will need to hard code the custom field ID into the program, no?

No, we can find id by name. API can return list of all fields with their ids, https://confluence.atlassian.com/jirakb/how-to-find-id-for-custom-field-s-744522503.html

Ah I see what youre refering too. I've tried that, only problem is it returns a list of custom fields (i.e. {customfield_1, customfield_2...... etc). So there is no real way to check the name vs the ID.