Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
Level
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Send a list of issues in Slack with Jira automation’s newest action (Cloud)

50 comments

@Sam Harding Thanks for spotting that! damn capitalisation!! 

Like Sam Harding likes this

@Sam Harding You might want to update your doc then, because it says otherwise :)
I didn't even try it because of this :(

https://support.atlassian.com/jira-software-cloud/docs/automation-actions/#Automationactions-Lookupissues

"Use smart values here: No"


Thanks for the heads up!

Like Sam Harding likes this
Sam Harding Atlassian Team Jul 30, 2020

@blemasle Thanks for pointing that out, we'll fix that up. Sorry for confusion caused here! Cheers

Is there any way to add in formatting?

https://api.slack.com/reference/surfaces/formatting#visual-styles

 

Trying to bold a specific text and it's not working as expected

 

*bold*{{version.description}}*bold*

results in this being sent to slack..

*bold*version description here*bold*

Hi @Tom Wilson 

it’s *{{version.description}}*

@Tom Williams That worked!  Is there a reference guide for how to format messages to slack? 

I can't see to get issueType to display during my automation inside look up values.

here is all the options i tried, but getting empty string when it prints out to slack..

---- [{{issueType.name}}] - [{{issueType}}] -[{{issue.issueType.name}}] - 

Anyone else have this problem? 

Hey @Tom Wilson 

I had the same issue, looks like the documentation is incorrect and it should be {{issuetype}} so to get the name would be {{issuetype.name}} 

I am having a hard time getting this to work as expected. I am sending a daily email with this is the email body:

<ul>
{{#lookupIssues}}
<li>{{key}} - {{summary}}</li>
{{/}}
</ul>

I have tried several variations of  {{#lookupIssues}} } {{/}} but have had no success. For me, I receive multiple emails. For example, if my JQL returns 5 issues, I receive 5 emails. Am I missing something?

Michael,

May you please put a screenshot of your rule.

 

This is how mine is set and I only get one email

{{#lookupIssues}}
| {{url}} | {{key}} | {{status.name}} | {{issuetype.name}} | {{summary}}
{{/}}

@Neetu Verma 

Screenshot 2020-10-21 170606.png

JQL:

project = EZ AND Sprint in openSprints() AND status not in (Open,Done) AND timespent is EMPTY

 Email:

<ul>
{{#lookupIssues}}
<li>{{key}} - {{summary}}</li>
{{/}}
</ul>

Hi @Michael , 

Simple fix! You need to move the JQL from the Schedule Trigger and add the "Lookup Issues" action before the email send action.  

Like Neetu Verma likes this

@Tom Williams I’m not sure I understand your solution. Can you give me an example or screenshot?

@Tom Williams Thank you! This fixed my issues.

I guess I should have paid closer attention to this checkbox "Run a JQL search and execute actions for each issue in the query" haha.

Thanks again.

Like Tom Williams likes this

Yep, just move email as an action item

Hey!

 

You wrote - ". It could also mean commenting, transitioning, or updating every issue in the list. Magic!"

 

How can edit a field for all issues in the list? I couldn't find a solution that doesn't include Scheduled Trigger. I would like to use it with Manual Trigger or use it as an post action for another rule (for example - after sending the Slack message with the list of issues, change a custom field value for all issues in list).

 

I can't seem to find a solution anywhere

@Tom Williams I have used the below JQL 


status != Done AND created >= "-7d" AND created <= "-1d" AND NOT status changed

 

Where I get 4 issues when I validate

I am trying to send the same to slack. 

When I use the below 

<{{#issues}}{{url}}|{{key}} - {{summary}}{{/}}>

It works fine. I get the URLs printed 

But when I use

{{#lookupIssues}}{{key}}{{/}} 

Even if I use {{lookupIssues.size}}  it prints 4 blank lines It prints 4 empty lines.

 

What am I doing wrong here? I am on the Jira Cloud Enterprise version

Is the {{#lookupIssues}} feature supported on Jira Automation for Server already? 

 Jun 28, 2020 This new feature is unfortunately only available for the Cloud version of Jira automation right now (as opposed to the Automation for Jira app) 

@John McKiernan 

  1. When will it be available for DC? I can understand some lag, but June '20 to March '21 is more than a little time for your biggest customers to wait.  
  2. What is the workaround? 

Thanks, Martin.

Is it possible to filter or perform a group by on the {{#lookupIssues}} list?

I want to send out an email for each release which separates out bugs, stories and tasks. Similar to the below rather than as a single long list.

 

Bugs:

  • Bug 1
  • Bug 2

Stories:

  • Story 1
  • Story 2

Tasks:

  • Task 1

@Christian, I ended up having separate rules for each group.  

@Darrin Lange 

 

Is there no way to get the three groups into a single email?

 

I'm attempting to figure this out but just can't. The closes I can get to filtering on lookup issues is as below. 

 

<ul>
{{#lookupIssues}}
    {{issuetype.name}} //Just prints it to make sure there's nothing wrong with the list
    {{#if(issuetype.name.equals("Bug"))}}
        <li><a href="{{issue.url}}" target="_blank">{{key}}: {{issuetype.name}} - {{summary}}</a></li>
    {{/}}
{{/}}
</ul>

 

This only prints the issuetype.name from just inside the {{#lookupIssues}} loop. It doesn't seem to enter the #if.

Hi @Christian Macedo , I wasn't able to get that to work either. Instead of using the #if, incorporate your issuetype = Bug into your lookupissues JQL. Then, create a new rule for each issue type you want to push to Slack. 

@Darrin Lange That's the issue. I want to have these all grouped in a single email. Not slack. 

Comment

Log in or Sign up to comment
TAGS
Community showcase
Published in Jira Automation

Announcing the Jira automation template library!

Hi all,  After many months of work, I am delighted to announce the launch of the Jira Automation Template Library!  The Template Library is a new website dedicated to all things Jira au...

1,012 views 17 26
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you