John McKiernan Atlassian Team

100% agree. Suggest using the new lookup issues action also. This means you can just send one daily/weekly Slack message surfacing whatever issues are most important. Less noise, more value. 

Hey @Mykenna Cepek , How could I forget! One of our first customer stories for Automation for Jira all those years back :) Hope all is well and thanks for the message. As ever, you are quite right. We have used the term Global Admins as a team internally for so long but indeed it should be Jira Admins or Jira site admins.…

Hey @Liam Green Glad you are enjoying Automation so far! Just in case you weren't aware, we have lots of resources to help you get started. I posed them all on this page: https://community.atlassian.com/t5/Automation-articles/Welcome-to-the-Jira-automation-community/ba-p/1388465 With regards to your question, are you…

Thanks @John Funk Hey @Narendra Kumar There shouldn't be any limitation for fields we can look through. Could you pop up a screenshot of the rule failing when there were more fields? (if private, pop through support channel) Thanks

Hey @Olga Buslovich , For this question, I think it would be best to pop a question through to our support so one of the engineers can answer it. We might need to get into the weeds a bit :) John 

Ah apologies Ramana, I see what you were asking now. I don't believe this would be possible. You can't iterate through a list and comment on each. You could set up a second rule with the same JQL that would leave a comment. Not perfect but it might do the trick. For example: * Scheduled trigger with JQL * Add comment to…

Hey @Dan Davidson , Glad you are enjoying these new features! Not a dumb question at all. In fact, I had to check it with one of the engineers! So as you have your rule set up now, this will run for each associated issue. If you want to get more granular you can use the branch / related issues block Hope that helps! John 

Hey @Lloyd Jones , Glad you are enjoying the features! this page should help you connect Jira cloud natively with Jenkins: https://confluence.atlassian.com/adminjiracloud/integrate-jira-cloud-with-jenkins-972355471.html Also this page shows you how to integrate Jira with self-hosted tools (like Jenkins)…

hey @Stefan Salzl , It looks like your question has been answered below. Indeed, an execution counts whenever an issue is triggers regardless of the condition beneath. So the suggestion below to convert to a single project rule execution which is unlimited is the best advice. For other rules, you could use the 'field value…

Hey @Venkata Ramana Kaza , yes absolutely it would be as easy as adding one more action to the end of the rule to comment on the issue: Hope that helps! John 

Hey @Scott.Brogan , Glad you enjoyed the webinar! Have you attended the advanced automation webinar yet? Lots more to learn :) With regards to your question, it depends a bit on your rule. There isn't really a concept of a global rule running in a project (unless if you mean, running on an issue that's in a particular…

Hey @Rigoberto Nava , Thanks for your message. I hear you entirely and will do my best to reply openly below. You have probably read everything on this thread but I'll summarize also just for clarity. The app Automation for Jira is now a native part of Jira Cloud. All former Automation for Jira customers went on an…

Ah nice, that's a great use case. Thanks for sharing! 

Hey @Braden , I hear you. The Server team has a list of priorities they are working through but I don't believe this is on the list at the moment. I can update this post if there is any change. Sorry I know that's not the answer you are looking for! Cheers, John

Hey all, Just wanted to quickly update you on work relevant to this conversation. We recently shipped new automation triggers that allow you to integrate natively with BitBucket, GitHub and Gitlab. You can read more about that…

Hi all, Just wanted to update this thread to let you know there is now a native automation trigger for GitLab with Jira Cloud. We are running a webinar soon to walk through how it works and show some use cases in how to automate from Gitlab to Jira. Feel free to register…

Hi all, Just wanted to update this thread to let you know there is now a native automation trigger for GitLab with Jira Cloud. We are running a webinar soon to walk through how it works and show some use cases in how to automate from Gitlab to Jira. Feel free to register…

Hi all, Just wanted to update this thread to let you know there is now a native automation trigger for GitLab with Jira Cloud. We are running a webinar soon to walk through how it works and show some use cases in how to automate from Gitlab to Jira. Feel free to register…

Hey @JasonB3 , good news, you should be able to do this now. Any of these smart values should work: * {{lookupIssues.Story Points}} * {{lookupIssues.Story point estimate}} * {{lookupIssues.Story Points.sum}} * {{lookupIssues.Story point estimate.sum}} Hope that helps! John 

Hey @Ole Schäfer Glad you are enjoying these new triggers! Unfortunately, at the moment, we don't support any user-based smart values but your use case makes full sense to me. It is also not the first time I have seen this request since we shipped. I have created an improvement request in our backlog so we can hopefully…

Hi all, Good news! You now have double the amount of DevOps automation triggers available to you. We have just shipped support for Build and Deploy triggers so you link up tools like Jenkins, Circle CI and more. Read more about it here: More good news - we have added an extensive list of smart values that will work nicely…

Hey Amanda, I can see where you are coming from here. You do have the option to use a multiple issue event trigger (as below) but that is not going to do the job for your use case. We do have an improvement in the backlog whereby there would be an AND/OR condition so you could simply have one rule with multiple triggers so…

Hi @Andrew Laden (and thanks as ever @John Funk !) This is a really good suggestion Andrew. We had a couple of items in the backlog that touch on this but not in such detail. I have raised an improvement for it here: https://codebarrel.atlassian.net/browse/AUT-1995 I can't say if and when the team get to building something…

Hey @JasonB3 , Glad you enjoyed the webinar! Always fun running one. At the moment, this is unfortunately not possible. It is an existing 'bug' / limitation :https://codebarrel.atlassian.net/projects/AUT/issues/AUT-1946 The good news, however, is that it is being worked on by one of our engineers at the moment so it should…

Hey @Martina Schmidt as usual @John Funk is quicker than me and on the mark! Actually, I think I know what happened here. It's possible that if this rule was created at a Global level, the "Epic" or issue-type that was chosen here isn't a global issue type (This is pretty much the last piece of the puzzle that we need to…

Hey @Tom Williams , At the moment, unfortunately you can't use custom fields with the lookup issues action though there is an issue to make this possible. I'll make sure to update this post once that is shipped :) Cheers, John 

Hi folks, For anyone using GitLab who wants to learn more about how these new DevOps automation triggers work, we are running a co-hosted webinar with GitLab in a few weeks. Register here if keen: https://www.atlassian.com/webinars/software/automate-across-gitlab-and-jira Note: it will be equally valuable if you use…

Hi @Daniel Di Martino @John Pampers At this stage, there are no plans to add these triggers to Data Centre / Server. John

This is a great way to use automation - Kudos!

Hi @cendre , 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