Template Functions

Template functions allow you to use pre-built logic built into App Maker to complete certain tasks that you wouldn't normally be able to do with by just templating data.

A good example of this is linked and child issues in Jira. The full content of these issues is not available in the issue context, so you can't just template them in like you would with other fields.

Instead, you can use a template function to tell App Maker to go and fetch the full content of these related issues and then display them in your app.

Basic Usage

You might be familiar with the concept of a "function" from other tools, but if not, that's fine. Functions have two main parts:

• They have a name, used when you want to use (or "call") the function.
  • To "call" a function, you use the double curly braces like when you are using a template.
  • Then immediately inside the opening braces, write the name of the function you want to "call", followed by a colon. e.g. myFunction:
• And they have one or more pieces of data that you want the function to use when it runs. Providing this data to the function is called "passing" it to the function.
  • You often then need to "pass" some data to the function for it to use. The pieces of data you pass are called "arguments".
  • You "pass" the "arguments" to the function by simply adding them inside the template braces after "calling" the function, making sure there is a single-space between the colon and the argument you want to pass. e.g. myFunction: someData
  • If a function needs more than one piece of data to be passed to it, you can separate each piece of data with a space. e.g. myFunction: someData someOtherData

Example

• The example below shows an example that uses a template function called childIssues:
• This function allows you to fetch the full details of all the issues that are the "children" of the issue that the App is being displayed in.
• It works by taking the "parent" issue as the data you pass to the function, and returns a list of all the child issues under that issue.
• An example of when you would want to use this is if you wanted to display a table of all the child issues of the issue the user is currently viewing.

{
  "resourceType": "site",
  "module": "jira:issueContext",
  "title": "my-first-app",
  "action": "set",
  "componentData": {
    "type": "DynamicTable",
    "columnHeaders": ["...columnHeaders"],
    "tableRows": "{{childIssues: jiraIssue}}"
  }
}

Note:

• The childIssues: function actually takes any object that has a property called key, that the function can use to fetch the child issues of that object.
• It doesn't necessarily need a full Jira Issue object.
• It could be as simple as an object like {key: "ISSUE-123"}.

Outcome

• The outcome of this function would be a list of all the child issues of the issue that the App is being displayed in.

{
  "resourceType": "site",
  "module": "jira:issueContext",
  "title": "my-first-app",
  "action": "set",
  "componentData": {
    "type": "DynamicTable",
    "columnHeaders": ["...columnHeaders"],
    "tableRows": [{
      "key": "ISSUE-123",
      "fields": {
        "summary": "Child Issue 1 Summary",
        "status": "Open"
      }
    },
    {
      "key": "ISSUE-456",
      "fields": {
        "summary": "Child Issue 2 Summary",
        "status": "In Progress"
      }
    }]
  }
}

Available Functions

For a full list of available functions, see the Template Functions reference.