Hi, I'm trying to build a variable (that I'll later send to a slack message) with all an issue PR's data. To retrieve the data, I use a webhook that calls api1 issue/detail with stash appType: rest/dev-status/1.0/issue/detail?issueId={{id}}&applicationType=stash&dataType=pullrequest The call to the webhook is successful (I get 200) and returns as expected a big json with all PR's data in this variable: {{webResponse.body.detail.pullRequests}} I have a Story which is linked in BB to 2 open PR's. My problem begins when I try to use smart values list handling methods, to format a message that includes both PR's relevant data: {{#webResponse.body.detail.pullRequests)} • {{author.name}}'s {{status.toLowerCase()}} {{#if(equals(status,"OPEN"))}}, which need to be reviewed by {{#reviewers}}{{name}}{{/}}{{/}}\n{{/}} The expected result should be a text like this: • John Doe's open PR with id #1, which needs to be reviewed by Mark Twain, Virginia Woolf • Jane Smith's open PR with id #2, which needs to be reviewed by Ernest Hemingway , while instead I get a text like this: • John Doe, Jane Smith's open, open PR with id #1, #2 I would expect the '#' operator at the beginning of the webResponse variable, to make the subsequent methods iterate all entries for pullRequests array one by one, but instead they're somehow flattened. The same problem (I bet) prevents the {{#if}} for status OPEN to be successful. Any hints about what I'm doing wrong? Best regards, Federico

Hi @Fede B. -- Welcome to the Atlassian Community! I see a typo in your outermost iterator, with a parenthesis instead of a curly bracket. Substituting that bracket, and adding the comma handling for the reviewer delimiting, is below. I added extra spacing to see it better, so remove that after you have it tested and working as desired. {{#webResponse.body.detail.pullRequests}} • {{author.name}}'s {{status.toLowerCase()}} {{#if(equals(status,"OPEN"))}}, which need to be reviewed by {{#reviewers}}{{name}}{{^last}}, {{/}}{{/}} {{/}} \n {{/}} Also, have you confirmed the conditional check on status is correct? I recall from similar posts that the if() could fail if the case does not match for the status. For expressions like this with nested iterators, I find it easier to write them in another tool to help see the matching operators / tokens, and then copy-and-paste into the rule. Kind regards, Bill

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation smart variable from BitBucket web request fails to format properly

Fede B.

Hi,

I'm trying to build a variable (that I'll later send to a slack message) with all an issue PR's data. To retrieve the data, I use a webhook that calls api1 issue/detail with stash appType:

rest/dev-status/1.0/issue/detail?issueId={{id}}&applicationType=stash&dataType=pullrequest

The call to the webhook is successful (I get 200) and returns as expected a big json with all PR's data in this variable:

{{webResponse.body.detail.pullRequests}}

I have a Story which is linked in BB to 2 open PR's. My problem begins when I try to use smart values list handling methods, to format a message that includes both PR's relevant data:

{{#webResponse.body.detail.pullRequests)} • {{author.name}}'s {{status.toLowerCase()}} <{{url}}PR with id {{id}}>{{#if(equals(status,"OPEN"))}}, which need to be reviewed by {{#reviewers}}{{name}}{{/}}{{/}}\n{{/}}

The expected result should be a text like this:

• John Doe's open PR with id #1, which needs to be reviewed by Mark Twain, Virginia Woolf
• Jane Smith's open PR with id #2, which needs to be reviewed by Ernest Hemingway

, while instead I get a text like this:

• John Doe, Jane Smith's open, open PR with id #1, #2

I would expect the '#' operator at the beginning of the webResponse variable, to make the subsequent methods iterate all entries for pullRequests array one by one, but instead they're somehow flattened.

The same problem (I bet) prevents the {{#if}} for status OPEN to be successful.

Any hints about what I'm doing wrong?

Best regards,

Federico

Accepted answers

Bill Sheboy

Hi @Fede B. -- Welcome to the Atlassian Community!

I see a typo in your outermost iterator, with a parenthesis instead of a curly bracket.

Substituting that bracket, and adding the comma handling for the reviewer delimiting, is below. I added extra spacing to see it better, so remove that after you have it tested and working as desired.

{{#webResponse.body.detail.pullRequests}}
  • {{author.name}}'s {{status.toLowerCase()}} <{{url}}PR with id {{id}}> 
    {{#if(equals(status,"OPEN"))}}, which need to be reviewed by 
      {{#reviewers}}{{name}}{{^last}}, {{/}}{{/}}
    {{/}}
    \n
{{/}}

Also, have you confirmed the conditional check on status is correct? I recall from similar posts that the if() could fail if the case does not match for the status.

For expressions like this with nested iterators, I find it easier to write them in another tool to help see the matching operators / tokens, and then copy-and-paste into the rule.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Fede B. -- Welcome to the Atlassian Community!

I see a typo in your outermost iterator, with a parenthesis instead of a curly bracket.

Substituting that bracket, and adding the comma handling for the reviewer delimiting, is below. I added extra spacing to see it better, so remove that after you have it tested and working as desired.

{{#webResponse.body.detail.pullRequests}}
  • {{author.name}}'s {{status.toLowerCase()}} <{{url}}PR with id {{id}}> 
    {{#if(equals(status,"OPEN"))}}, which need to be reviewed by 
      {{#reviewers}}{{name}}{{^last}}, {{/}}{{/}}
    {{/}}
    \n
{{/}}

Also, have you confirmed the conditional check on status is correct? I recall from similar posts that the if() could fail if the case does not match for the status.

For expressions like this with nested iterators, I find it easier to write them in another tool to help see the matching operators / tokens, and then copy-and-paste into the rule.

Kind regards,
Bill

Fede B.

Hi @Bill Sheboy,

Thanks for your hint, the parenthesis was just a typo due to autocorrection when copying&pasting, but in my automation rule the code was ok.

I used

{{#webResponse.body.detail.pullRequests}}
  • {{author.name}}'s {{status.toLowerCase()}} <{{url}}PR with id {{id}}> 
    {{#if(equals(status,"OPEN"))}}, which need to be reviewed by 
      {{#reviewers}}{{name}}{{^last}}, {{/}}{{/}}
    {{/}}
    \n
{{/}}

as you suggested, but got the same result:

• John Doe, Jane Smith's open, open PR with id #1, #2

This is the (sanitized) payload that I get from my web request:

[
  {
    "author": {
      "name": "John Doe",
      "avatar": "https://bitbucket.example.com/users/jdoe/avatar.png?s=1&v=0000000000001"
    },
    "id": "#1",
    "name": "Feature/XXX-1 Test PR 1",
    "commentCount": "0",
    "source": {
      "branch": "feature/XXX-1-test-pr-1",
      "repository": {
        "name": "myRepo",
        "avatar": "https://bitbucket.example.com/projects/TEST/avatar.png?s=2&v=0000000000002",
        "avatarDescription": "TEST",
        "url": "https://bitbucket.example.com/projects/TEST/repos/myRepo/browse"
      },
      "url": "https://bitbucket.example.com/projects/TEST/repos/myRepo/commits?until=refs/heads/feature/XXX-1-test-pr-1"
    },
    "destination": {
      "branch": "master",
      "repository": {
        "name": "myRepo",
        "avatar": "https://bitbucket.example.com/projects/TEST/avatar.png?s=3&v=0000000000003",
        "avatarDescription": "TEST",
        "url": "https://bitbucket.example.com/projects/TEST/repos/myRepo/browse"
      },
      "url": "https://bitbucket.example.com/projects/TEST/repos/myRepo/commits?until=refs/heads/master"
    },
    "reviewers": [
      {
        "name": "Mark Twain",
        "avatar": "https://bitbucket.example.com/users/mtwain/avatar.png?s=4&v=0000000000004",
        "approved": "false"
      },
      {
        "name": "Virginia Woolf",
        "avatar": "https://bitbucket.example.com/users/vwoolf/avatar.png?s=5&v=0000000000005",
        "approved": "false"
      }
    ],
    "status": "OPEN",
    "url": "https://bitbucket.example.com/projects/TEST/repos/myRepo/pull-requests/1",
    "lastUpdate": "2024-01-01T18:47:09.000+0200"
  },
  {
    "author": {
      "name": "Jane Smith",
      "avatar": "https://bitbucket.example.com/users/jsmith/avatar.png?s=6&v=0000000000006"
    },
    "id": "#2",
    "name": "Feature/XXX-1 Test PR 2",
    "commentCount": "0",
    "source": {
      "branch": "XXX-1-test-pr-2",
      "repository": {
        "name": "myRepo",
        "avatar": "https://bitbucket.example.com/projects/TEST/avatar.png?s=7&v=0000000000007",
        "avatarDescription": "TEST",
        "url": "https://bitbucket.example.com/projects/TEST/repos/myRepo/browse"
      },
      "url": "https://bitbucket.example.com/projects/TEST/repos/myRepo/commits?until=refs/heads/XXX-1-test-pr-2"
    },
    "destination": {
      "branch": "master",
      "repository": {
        "name": "myRepo",
        "avatar": "https://bitbucket.example.com/projects/TEST/avatar.png?s=8&v=0000000000008",
        "avatarDescription": "TEST",
        "url": "https://bitbucket.example.com/projects/TEST/repos/myRepo/browse"
      },
      "url": "https://bitbucket.example.com/projects/TEST/repos/myRepo/commits?until=refs/heads/master"
    },
    "reviewers": [
      {
        "name": "Ernest Hemingway",
        "avatar": "https://bitbucket.example.com/users/ehemingway/avatar.png?s=9&v=0000000000009",
        "approved": "false"
      }
    ],
    "status": "OPEN",
    "url": "https://bitbucket.example.com/projects/TEST/repos/myRepo/pull-requests/2",
    "lastUpdate": "2024-01-01T18:47:17.000+0200"
  }
]

Best regards,

Federico

Fede B.

At the moment the only (ugly/unsustainable) solution that I found, is to store the above json in an Automation variable, which converts the json to string, and then use split/replace/substring methods to format the result.

Fede B.

I also tried a simplified version of the format:

{{#webResponse.body.detail.pullRequests}}
• {{author.name}}'s
{{/}}

The above method returns:

• John Doe, Jane Smith's

Instead of

• John Doe's

• Jane Smith's

There must be something wrong with the format of the webresponse itself.

Because I have tried to use a similar method for a lookupissue variable, and it worked fine:

{{#lookupIssues}}
• {{key}},
{{/}}

, returns:

• XXX-1,

• XXX-2,

• XXX-3,

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

automation

text

list

smart-value