Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

There might be cases where we want to assign a Jira issue to a specific Tempo Team based on certain conditions. In the example below we use the Jira issue assignment as the trigger to run of an automation rule to set a Tempo Team on the Jira issue. Further, we can implement a what-if scenario by setting the Team name based on the assignee user or the assignee belonging to a Jira group.

Since the Tempo Team field can´t can't be set out of the box we will need to leverage the advances advanced options when editing the Jira issue in via an automation. Therefore we need the Tempo team customfield ID. Jira custom fields can be retrieved from the Jira API

...

In the response search for “Team”. This , your query should give you something like this:

Code Block
{
        "id": "customfield_11718",
        "key": "io.tempo.jira__team",
        "name": "Team",
        "untranslatedName": "Team",
        "custom": true,
        "orderable": true,
        "navigable": true,
        "searchable": true,
        "clauseNames": [
            "cf[11718]",
            "Team"
        ],
        "schema": {
            "type": "option2",
            "custom": "com.atlassian.plugins.atlassian-connect-plugin:io.tempo.jira__team",
            "customId": 11718
        }
    },

...

Before we go into Automation for Jira we will also need the respective Tempo Team IDs as we can´t can't use the Tempo Team names in Automation for Jira. We can get the Team ID by navigating to the Tempo Team and look for the ID in the url.

...

Code Block
https://api.tempo.io/core/3/teams

This will get us provide a response aslike this:

Code Block
{
  "self": "https://api.tempo.io/core/3/teams/2",
  "id": 2,
  "name": "Web Development",
  "summary": "",
  "lead": {
    "self": "https://cops.atlassian.net/rest/api/2/user?accountId=5cb085549b0de43f0aea7154",
    "accountId": "5cb085549b0de43f0aea7154",
    "displayName": "Angel Williams"
  },
  "program": null,
  "links": {
    "self": "https://api.tempo.io/core/3/teams/2/links"
  },
  "members": {
    "self": "https://api.tempo.io/core/3/teams/2/members"
  },
  "permissions": {
    "self": "https://api.tempo.io/core/3/teams/2/permissions"
  }
},...
Note

Make sure that the Tempo Team is linked to the Jira project where that you want to use the Jira automation rule for. The Tempo Team can only be set on the Jira issue when the Tempo Team is linked to the Jira project.

Once we have ensured that we have everything we need to ensured and all settings are correct we can go ahead with Automation for Jira.

...

The trigger for the rule is when a user is assigned to a Jira issue or the assignee changes.

We implemented in the this example a condition rule checking on the assignee. Means we We want to set a different Tempo Team based on the assignee of the Jira issue. Without going into too much details detail, you can check the value against a specific user or if the assignee belongs to a certain Jira group. Just have keep in mind that the if-block is exited once a condition is met.

...