I am using Confluence Confiforms IFTTT macro to create a JIRA issue. My problem is a custom field in Jira that has a "/" slash in the field name (ie. component/s) I can't figure out how to include this field slash in the macro. Everything I tried generates an error becasue of the slash. I have tried escaping using <esc>/ but that doesn't work either.
Alex, thank you.
However, still not working...getting this error:
Here's my code:
{
"fields": {
"project":
{
"key": "MPAS"
},
"summary": "[entry.Summary]",
"description": "[entry.Description.escapeJSON]",
"labels": ["ProjectIntakeRequest.escapeJSON"],
"components": ["Stardust"],
"issuetype": {
"name": "Story"
}
}
}
Please have a look at the answer I have linked earlier - https://community.atlassian.com/t5/Answers-Developer-Questions/How-to-set-components-in-Jira-REST-API-5-x-while-creating-a/qaq-p/529155
It is all there - you are setting the field incorrectly...
Should be
"components": [{"name":"Stardust"}]
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I need to mention also that the custom field 'Component/s' is already define in the story screen. So error message is confusing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is not confusing really, as it tells you that this field is not on the screen - and this means it is either incorrectly referenced or missing indeed.
See my previous comment - in your case it is incorrectly referenced in the mapping
Should be "components"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The slash is in the No Format section of the IFTTT:
{ "fields": { "project": { "key": "MPAS" }, "summary": "[entry.Summary]", "description": "[entry.Description.escapeJSON]", "labels": ["ProjectIntakeRequest.escapeJSON"], "Component/s": ["Stardust"], "issuetype": { "name": "Story" } } }
Here's the error I get:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Where do you have and need for a forward slash? In JSON mapping between Jira and ConfiForms?
Alex
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Components are not set by "name", but as every other field in the JSON mapping it needs to be set by internal name.. which is "components"
See also some other answer on this https://community.atlassian.com/t5/Answers-Developer-Questions/How-to-set-components-in-Jira-REST-API-5-x-while-creating-a/qaq-p/529155
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Please show me how the syntax would be in the No Format below:
"labels": ["ProjectIntakeRequest.escapeJSON"],
"Component/s": ["Stardust"],
where I am assigning the field Component/s a value of "Stardust"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think you still misunderstand what I am saying... instead of
"Component/s": ["Stardust"],
you need to put
"components": ["Stardust"],
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I guess I am still not getting it or not communicating properly. In my case, our custom field name is 'Component/s' which is a really bad name since component is also a keyword in Jira.
So, how do I reference this field 'Component/s' in my Jira story creation from ConfiForms? I need to assign it a value of "Stardust".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If this is a custom field then it should have an internal name in a way like
customfield_XXX
where XXX is the number assigned to it by Jira when you have created it. and you should use this (internal) name in the mapping (not the label "Component/s" or whatever else you may have as a file label).
Jira expects an internal field name for this field
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.