I've created a table view in Confluence that displays fields as submitted via confiforms entries, including the Jira ID # that feeds back to the confiform entry at submission. I wanted to bring the Jira Issue Status field into this field view as a separate field so I followed the following steps from vertuna:
"We add ConfiForms Field macros to the TableView and set the field names parameters like this: myJiraIssue.fields.status.name".
This worked and I now have a separate field that I can export that lists status. I want to do the same thing for another field labelled as "Sprint" (official name is customfield_15) and am unable to get it to work trying:
Has anyone run into a problem like this?
Appreciate any help / guidance!
What you need to know is exact name of the field and the structure Jira uses to return it's value when requested via REST API call
I am pretty sure the field name is not "customfield_15", as custom fields have a much larger numbers...
Try to do a request in the browser to
https://_your_jira_/rest/api/latest/issue/_issuekey_
Changing _your_jira_ and _issuekey_ respectfully, and see what field returns information about the sprint and what is the structure
Alex
You're right, it's customfield_10005. I don't have global admin rights to my Jira server, just local project admin rights.
Here is the field in xml:
<customfield id="customfield_10005" key="com.pyxis.greenhopper.jira:gh-sprint">
Does this help describe the issue better?
Thanks!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Not quite. I have no idea myself how to get such xml
Have you tried to do a request as I mentioned in the browser?
(you don’t need any extra permissions)
find in that response your custom field and share its structure
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Unfortunately I get an error or redirected back to the main project page when I try to change the url.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The URL you should craft should be almost the same as the one you see when you browse the issue - at least it's server part
https://_your_jira_/
Feel free to open support issue and provide the URL you see in the browser when viewing the issue in Jira and I will construct the URL fro you that does the same but returns a JSON (RESt API call)
Alex
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online 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.