This is the documentation for ConfiForms Server/Data Center app
However, this might also work for ConfiForms cloud and in most cases it does. But please see this page to understand the differences between server and cloud versions of the ConfiForms app.
In ConfiForms you have simple and "rich" fields. Simple fields (such as text or textarea) hold just the value and nothing else. You can apply the virtual functions and transform the field and nothing else.
With "rich" fields you can do a lot more - rich fields, such as smart fields or Jira issue field, or Insight object or fields backed by the database query or the web service connection, allow you to access other data associated with this field.
It is sort of a "bridge" to another form, query or your Jira.
Let's look at Jira issue field type form ConfiForms in more details
With Jira field in ConfiForms you open a "bridge" to your Jira and can access any property you Jira issue has
ConfiForms communicates with your Jira using an application link (or a web service connection if you are using ConfiForms cloud) and works with a JSON structures
And anything you se here can be accessed through the ConfiForms Field macro, setting field name parameter to a "navigational expression"
For example, we have a form with Jira field and it is called "myJiraIssue"
And by default the data from the issue is represented like
But what if we want to show the assignee or a type of issue... This is possible!
We add ConfiForms Field macros to the TableView and set the field names parameters like this
| Issue type | myJiraIssue.fields.issuetype.name |
| assignee name | myJiraIssue.fields.assignee.name |
| project type | myJiraIssue.fields.project.projectTypeKey |
And based on the data in our Jira the TableView will now render the following view
So, how to "read" something like this "myJiraIssue.fields.issuetype.name"?
You start with a Jira issue field in ConfiForms, and that is called "myJiraIssue" in our example form, then.. based on the data structure returned by Jira REST API we navigate to "fields" node and then further down to "issuetype" and finally to "name" node to show the value
Accessing field values and properties page shows some other properties you can always access from a Jira issue field in ConfiForms, such as key, status, summary.
Another example, what if we need to show the "fix version" details
The information is located under the "fields.fixVersions.name" - see the example JSON structure above
And therefore the field name parameter in ConfiForms Field macro shall be set to
Again, we use "myJIraIssue" field we have defined in our form as a "bridge" to Jira and then tell the app to navigate through the details to the name of the version to get "Version 2.0" value
Overview
Content Tools