Simmo Atlassian Team

Hi @Muhammad Ramzan_Atlassian Certified Master_ , I'm afraid it isn't prioritised at the moment. The best cause of action for you to take if you want to try and get it pushed along is to raise a support ticket. Cheers, Simeon

So you wanted to do this via a comment then? Not email or anything?

Hi @Andrei Sirotin I've put together an example for you on how you achieve this. @Alexander Pappert was pretty close with his example. You start with an Issue Transitioned trigger and choose the resolved status as the To status. In my example project, this is "Done". We then branch onto the issues it is linked to. In…

Hi @Sean Roberts Are you wanting to just communicate some information to the customer or does it need to be a comment? Cheers, Simeon.

Hi @Ahmad Sidawi Glad you got it working. For future reference, whatever you defined as your smart value you should be able to use directly in the For JQL branch, saving you having to define a variable just for that! Cheers, Simeon.

Hi @Ahmad Sidawi Is the Parent Link a custom field? Cheers, Simeon.

Hi @Jayce Canale, That's right, an If / Else block isn't available instead a branch as we only support one level of branching and an if else is a branch in its own right. Shout out if you need a hand rejigging your rule! Cheers, Simeon.

Hi @Scott Edwards, Yeah, in this case I think you should raise this as a support ticket. It'll need some detailed investigation. Cheers, Simeon.

Hey @John Funk & @Bob van Rooij , This is rather strange indeed. I haven't seen anything like this. Would be a good idea to get this into support so that we can take a proper look. Cheers, Simeon.

Hey mate. I'm not sure if this is a search within Jira or with Automation for Jira? It sounds like its a Jira search, so I'm not real sure. It might be an issue with indexing or caching inside Jira? The only thing I can think of to check would be that the field is allowed to be empty but if the rule is running successfully…

Hi @Richard Vencu, I'm afraid not. We have got an improvement tracking this, which would add the option to allow the rule to continue on a non 2xx response. https://codebarrel.atlassian.net/browse/AUT-1622 Cheers, Simeon.

Hi @Richard Vencu , Have you worked around your issue then or did you still need some assistance?

Hi @Chris Grace , I don't think that we have documented the question that you had around the scope of variables. I'll look into getting this resolved. Default values for smart values are in this section. https://support.atlassian.com/jira-software-cloud/docs/what-are-smart-values/#Whataresmartvalues?-Defaultvalues The…

Hey @Chris Grace, So, your first question, the way to avoid this is to use the default operator, then you don't need an IF. You do it like this: {{hours|0}} So that will default to 0 if it has no value :) So, your second question. IF blocks and related blocks, everything that happens on these is scoped to this block and…

Hi @Jasper Hovenga, I'm afraid that will be in the next set of changes. That is apart of https://codebarrel.atlassian.net/browse/AUT-97 It isn't supported yet. Cheers, Simeon.

Hey @Hilmar Everts, That wording might need a bit of updating. The underlying restrictions here are that we cannot impersonate other Connect addon users and we cannot impersonate Atlassian support stuff that you have granted temporary access to your site for support reasons (their permission set is too high). The other…

Hey @David Adason It might also be a good idea to look at the rule details tab when editing the rule and seeing what the scope of the rule is set to. Failing that, I recommend you create a support case and get support to look into it :) Cheers, Simeon.

Hi @Benjamin Tong, You'll need to do a bit of digging but it looks like if the enquiry comes in via email then there might be an entity property on the issue called request.channel.email.source which contains the email address that the ticket came in via. If that is the case, you could setup an if else if block based on…

Hi @John Funk & @Steven Drury , I'm not familiar with Advanced Roadmaps but it sounds like they could be in a format / form that we don't understand. What I'd suggest you try is visiting https://support.atlassian.com/jira-software-cloud/docs/use-smart-values-to-manipulate-and-format-dates/ and seeing if you can use the…

Hey @konstantin.vasilev , I'm afraid that you can only use numbers with the math IF, like so: {{#=}}IF(true, 1, 0){{/}} It isn't possible to use Strings as the two options I'm afraid. Cheers, Simeon.

Hi folks, I don't know much at all about this function since its a Jira specific thing. However, looking at the error message: Issue link type 'PROJ-154' could not be found in function 'linkedIssues'. I think the issue might be with your param. Why is issueToLink smart value providing the same value twice? In your example…

Hey all! @David Washburn, it does indeed include JSD comments :) @Hilmar Everts, unless I've misunderstood you, that option is included. When choosing the actor you can choose the option "User that trigged the event". This will then set the actor to whoever created/edited/commented, etc. @Jasper Hovenga, if I understand…

Hey @[deleted] , you can get details on this on our status page at https://status.automationforjira.com/ If the actor hasn't changed then this new feature won't have affected your rules. It can only kick in when the actor changes to someone other than our "Automation for Jira" user. I've also looked at the logs for your…

We had an incident towards the end of last week which could account for some of those errors. At the time that they errored, were the actors still set to Automation for Jira?

Hey @Massis Shahmirian , I'm afraid not. They'll still be "Automation for Jira".

Hey @Kimi Nakashima , I've updated the post to be a bit clearer. This is only for Jira Cloud. From what I can remember this has already been available in the server version for quite a while. Cheers, Simeon.

Hey @[deleted], Thanks for reaching out. There has indeed been some changes. I've posted about it here. Apologies for the delay on the post, I got a bit caught up in an incident. In short, we're rolling out the ability to change the actor. However, we haven't changed it by default on you, so your rules should not have…

Hi @Alex Rouk , yeah I'm starting to get the picture now. Is it possible for you to share a few screenshots of how you have configured your rule so we can figure this out?

Hi @Alex Rouk , Does the "same project" option not work for you? It will try to determine it based on the trigger context. So you shouldn't have to specify a project.

Hi @Alex Rouk , Not sure which Automation you're referring to. But if you're referring to Jira Automation (formally Automation for Jira) then there is an option in the UI that will do what you want to acheive: Cheers, Simeon