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

Counting Amount of Issues in Specified Status

Hello,
I am trying to automate a part of my Next-Gen project and have been struggling to get this one output to print properly. My automation successfully runs a check every morning to see if there are any new tasks created in a specified status called Under Investigation and returns a message to our Microsoft Teams channel. 
The issue is that in the statement sent to our Teams channel I want it to return the number of issues in that specific status. I have attempted several iterations of {{issue.status.name.size}} or .count or .value to no avail. If you could please point me in the right direction as to what syntax I need to perform this print out and why that would be great.

Thanks.

2 answers

1 accepted

1 vote
Answer accepted

Hi @Raymond Jenks  -- Welcome to the Atlassian Community!

Are you using an automation rule to do this? If so, you could try something like this:

  • Trigger: scheduled once per day (perhaps at a specifc time using a CRON expression)
  • Action: Lookup Issues with JQL to find issues in your status
  • Action: send a message to your MS Teams channel with the count: {{lookupIssues.size|0}}

That last part handles a default of zero when there are no issues in the status.

Best regards,

Bill

That worked, thanks Bill! I'm not sure why {{lookupIssues.size}} doesn't work with the JQL search built into the Schedule component but I'll take it.

Like Bill Sheboy likes this

I am glad to hear that worked for you.

When you use the Scheduled trigger with JQL that helps when you need to process each item one-by-one, such as for editing.  Lookup Issues is when you need the set for non-edit stuff, like counting or reporting.

Like John Funk likes this
0 votes
John Funk Community Leader Mar 04, 2021

Hi @Raymond Jenks  - Welcome to the Atlassian Community!

It might be because it is a Next-gen project and not all Automation functionality works with them. 

Can you try the same notice on a Classic Software project to see if it works? 

I just attempted the same syntaxes mentioned above on a Classic Project and still none of them worked. I'm certain the syntax I've chosen to get this output is incorrect. I just need to be pointed in the right direction on that.

John Funk Community Leader Mar 04, 2021

Can you share a screen shot of the rule with the details for the syntax?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Confluence

⚡️NEW Group for Confluence Cloud Admins

Calling all Confluence Cloud Admins!  We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...

109 views 2 9
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