John McKiernan Atlassian Team

Ah yes that sounds like the problem @swagner My advice would be to use the automation engine for as much as you can. It is easier to use, easier to track and it means everything will be in the one place. You can then, if needed, go back to Jira workflows for anything automation is unable to do. You were right to change the…

Hey Mike, Unfortunately there is no way of watching those issues for the moment. We are still trying to figure out the best way of bringing this over to the Atlassian systems. It might be worth putting through a support ticket with your request in case I am missing something. (I am on the marketing team rather than an…

Hey @swagner , You don't need to enable anything and I don't think this is a permissions issue. The audit log shows us that the rule isn't actually triggering at all so the problem lies somewhere before the trigger. * Do you have any Jira workflows, conditions, post functions, etc set up that might interfere with this…

Thanks @John Funk @Michael Spoonauer - unfortunately other John is correct here. It isn't supported at the moment though we are tracking it here: https://codebarrel.atlassian.net/browse/AUT-1063 Makes a lot of sense. I have added a reminder at the end of the issue to post an update here once shipped. Cheers, John

Hi @Wei_Kong I would suggest holding on for a few days before investing time exploring workarounds. I should have an update here very very soon about Github! Cheers, John 

Hey @josh_kirby , At the moment, it's not on the list. However, I have passed your request on to the Product Manager who is going to dig in to it and see what's possible. I'll update you if there is any change. CheerS 

Hi @Jim Edgeton , Thanks for your post. John from the automation team here. Glad to see you have been enjoying Jira automation so far. Unfortunately, we had a bug in the past hours which caused this behaviour. It is all fixed up now so everything should be back to normal. Please let me know if you see any other quirky…

Ah you got me @Assia Touati ! I knew I was going to make a mistake in there somewhere. I think I may have broken a record for longest community post ever :) 

Thanks for sharing those @Jack Hunter _HeroCoders_ There are indeed other apps mentioned but I think Tempo was the only one mentioned in the webinar. Appreciate you including the link, John

Hi @John Owens (and thanks for the heads up @John Funk Unfortunately there was a bug that happened overnight (Australian time). The engineer has just shipped a fix so everything should be working 100% again. Apologies for the frustration! John

Hi @Artur.Cybruch , Yes these new triggers in Jira's automation engine solve that problem with the old workflow triggers. You can simply choose the trigger you want then add a JQL condition checking that there are no open issues. Hope that helps! John

Hi all, As promised, we have put together a list of questions and answers from the webinar. You can find it here: https://community.atlassian.com/t5/Jira-Software-articles/79-Questions-and-Answers-about-Jira-Automation/ba-p/1363930 Be warned, there are a lot but it should be super valuable. There are over 40 use case…

Hi @Esther Strom , The DevOps rules are still part of Jira automation so they have the same limits. However, keep in mind that these limits only apply for multi-project and global rules. So for example, if you trigger a rule when a PR is created in BitBucket and it transitions an issue to 'In Progress' in your Jira…

Hi @YC Lian _ServiceRocket_ , I can understand that and accept it's not the right choice for everyone. Don't forget you have unlimited single-project rules so it is only the global rules you need to consider. Also, just in case you work with BitBucket, GitHub or Gitlab, I just wanted to let you know we have released 5 new…

Hey Bianca, This is a good point. It will count as an execution regardless. This wouldn't be the case with the 'field value changed' trigger as it would only kick off when the epic link is updated. If your rule is only running across one project, it doesn't matter as you have unlimited single-project rules. However, if you…

Hi @Bianca Sarmiento , This is a limitation at the moment I'm afraid. We are tracking it here: https://codebarrel.atlassian.net/browse/AUT-1264 This workaround should do the trick until it is fixed:

Hi @Assia Touati , Thanks for sending through those screenshots. I understand now. The bad news is that we don't currently support this. The good news is that we will be shipping this functionality very soon: https://codebarrel.atlassian.net/browse/AUT-476 I have added your vote to it and also left a note to update this…

Hi @Abby , No problem. The team are actually exploring ways to make this easier at the moment including an auto-complete and a smart value builder. I will have more news on this soon which I know will please many who battle smart values daily! In the meantime, here are two resources that might help: 1) This is a webinar…

Hi @Hine , At the moment, you can't use automation in Jira to open or close sprints. I've added your vote to the ticket at https://codebarrel.atlassian.net/browse/AUT-704 However, you could start an automation rule with one of our sprint triggers: 

Hi @ben , Thanks for attending the webinar, I hope you enjoyed it! Unfortunately at the moment, we can't copy attachments across in Cloud. It is a very popular request as you can see from this post so hopefully we can make this possible soon. Thanks, John

Hi @Mark Thompson Thanks for your message. We actually received close to 800 questions in the first automation webinar which is a lot more than I expected! Getting that many questions is fantastic, however, it meant we didn't get to answer everything in person so apologies. We are currently going through all of these…

Ah yes that makes sense! Glad you got it sorted :) 

Hey @Nathan Arnott , That is a strange one. I just copied your rule exactly and all worked as expected on my side. It's possible that automation is going a little quicker than Jira. You could add a 'refresh issue data' action before your second sub-task to add a delay or as John suggested that branch would do the job. I'll…

Hi @Abby , Thanks for calling this out. You are dead right, this is an error and you have saved other customers time solving this! I have asked Kevin on the team to update the docs to reflect this. Thanks John also for the heads up :) On a side note - the smart values are probably the last remaining 'complex' part of…

Hi Assia, Thanks for your message. Hopefully I didn't pronounce your name too wrong in the webinar yesterday! Would you mind sending a screenshot of your rule and audit log so I can see a bit clearer what is going on? If you'd prefer not to send publicly, pop it through to support and we can answer there. Cheers, John

Hi @Max McDaniel , At the moment, it will be the other way around. It will listen for events in Bitbucket such as Branch created which will then allow you to perform actions in Jira. Essentially they are the same triggers as below currently available for Bitbucket that will be enabled with Github. You can always use the…

Hi @Max & @Daniel, I can't give an exact date just yet but it is very much to be counted in weeks rather then months. I will update here as soon as I have a confirmed launch date and will also email :) Cheers, John

Hi @[deleted] , Thanks for your message. To be honest, we could do a better job explaining how the execution count works. Every Jira Cloud instance has unlimited single=project rule executions. The limits only come in to play for multi/global rules. * With Jira Software cloud (500 user) and Jira Service cloud (5 agents) on…

Hi @Julie Robert , Glad you enjoyed the webinar. We had good fun too! If I understand your question correctly, you are looking to transition all issues from one status to another using automation? Ideally this would come from when a commit is created? If that is correct, it should be an easy rule for you. Option 1:…

Hi @Ankush Dixit , thanks for your question. As a former Automation for Jira Pro Cloud customer, you are currently on the extended free trial of Jira Software Premium. This trial runs until the first billing cycle after June 3rd. During this time you continue to pay the price of the app but do not pay for Jira Premium.…