Hi All,
I'm new to ConfiForms.
I created a ConfiForms Form were the results are to be used to create a Jira issue using the IFTTT integration rules.
I'm getting error on System field "Component/s" and its a required field in that particular project.
Could someone help me how to describe JSON for that particular field?
Field names are case sensitive!
Components != components
You are also missing a comma after the "TestComponent1"}], <----- comma is missing
@Alex Medved _ConfiForms_ Thanks!
I edited the comma and adjusted the Components,
Still I'm getting the same error.
Could you please help me to resolve it?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You could not be getting the same error if you have changed the name and fixed the JSON mapping.
Also, please check if you actually can set the components on Jira issue when you create the issue in Jira via UI (of type "Task" in INF project)
Do you see "components" field there (in JIra Create Issue form)?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes I can see,
Please check the screen shot and components is system field with multi selected option and it's a required field for the "Task" issue type to the particular project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
How does the complete (jira issue JSON) mapping looks like?
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.
On Confluence/ConfiForms side you have a JSON mapping (in IFTTT macro body)
how does it look like now?
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.
Sorry, but I was asking about the macro body, no macro properties...
Something what you have on your initial screenshot, but current
Alex
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Currently I'm trying with different JSON syntex,
But I didn't get the result, not sure how to set.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
But setting components in Jira is done differently!
You should really consult the documentation for Jira API - there is nothing to do with ConfiForms here...
"components" : [{"name" : "Network [entry.tname]"}]
(and you had it almost right initially, but then moved to something else - really dont understand why)
Also, in your mapping you have a },} in the end.. WHY do you have a ","? Jira expects a valid JSON to be posted
Alex
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.
OK, and what do you ask?
I believe the error message is self explaining - you dont have a component by name "Network" registered... and therefore it is not valid as an input
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If I use this "components": [{"name":"Applications"}], It's working with out error and Jira ticket is getting created with the component as "Applications" only, but I should allow the users to select their choice.
How I can get those options?
Could you please help me with the code?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
Please see this wiki page on our documentation with an example: https://wiki.vertuna.com/display/TEST/Building+a+dropdown+field+in+ConfiForms+backed+by+webservice+call+to+Jira+Rest+API+-+components+field
Alex
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks! , Now it's working as per my requirements,
I've another field to set.
Priority System field, I'd like to have the sysntex to set this field in ConfiForm.
Could you please help me?
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Simple search over the community reveals good answers to this question.. For example this one https://community.atlassian.com/t5/Jira-questions/Can-t-set-priority-when-creating-an-issue-REST-API/qaq-p/1190923
Alex
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Prabhu Prabhakar ,What was done finally to fix this component/s issue to call from jira as I am also facing the same issue while trying to call jira from confiforms.
Can you please share the working code here so I also implement the same.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Prabhu Prabhakar , What was done to fix this component/s from jira to confiforms ,Can you please share the working code here as I am also facing the same issue while trying to call confiforms from Jira..I need user to select the application name from confiforms and the same to be populated as a jira ticket..
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Bad practice but if you still want to do it the documentation is your freind.
Copycurl \ -D- \ -u charlie:charlie \ -X PUT \ --data {see below} \ -H "Content-Type: application/json" \ http://localhost:8080/rest/api/2/issue/QA-31
This is an example input data:
Copy{ "update" : { "components" : [{"set" : [{"name" : "Engine"}, {"name" : "Trans/A"}]}] } }
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join the largest European gathering of the Atlassian Community and reimagine what’s possible when great teams and transformative technology come together. Plus, grab your Super Fan ticket now and save over €1,000 on your pass before prices rise on 3 June.
Register nowOnline forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.