Simmo Atlassian Team

Hi @tal Could you share a screenshot of how you have configured the Advanced compare? I suspect that you need to change your condition to be just the condition "contains" and if you have quotes around the yes then remove those as well. Also, this is case sensitive as well so your case needs to match, or you need to add a…

Hi @Alexey Paveliev, Is your issue that one rule won't be triggered by the result of another rule? Cheers, Simeon.

Hi @Gerardo Dalena, Bill is correct, the way that you'll need to do this is via the advanced condition. This will allow you to use smart values to access the cascading field. Cheers, Simeon.

Hey Matt, I'm afraid I'm not sure how they are doing that but if you can provide a sample of one of your bodies we might be able to figure it out? Cheers, Simeon.

I just helped another customer with a very similar issue. See https://community.atlassian.com/t5/Automation-questions/Changing-the-reporter-field-with-a-smart-value-and-keep-getting/qaq-p/1698187 That might help you?

Hey @Matt Adorjan So if this is just the reporter field, do you know if it just customers or if it could be your regular users as well?

Hi @Matt Adorjan What is the exact value that you're trying to do? In the use of the reporter field, you can only set it via account ID. If you're not using their Atlassian account ID, it will not set. Are these customers or normal Atlassian accounts? Cheers, Simeon.

Awesome mate, glad to hear that you got there! Try it without them, I don't think you'll need them and all it is doing is putting unnecessary load on Jira!

Hi @David B My apologies, I forgot to add the other important step. You cannot reference a user by email address. However, when we add a customer they are accessible via the smart value customer. You can use this to get the account ID which will be accepted: {{customer.accountId}} I have just tested that and got it to…

Hi @David B, I think you need to use the Add Customer Action to add the email address as a customer, then try what you're doing. Let me know how that goes. Cheers, Simeon.

Hey @Gil, You can now do this. We've made it possible to change the rule actor. Cheers, Simeon.

Hi folks, you can do that now. We've released the ability to chose your rule actor. It is on the rule details page.

Hi @Olga Buslovich I'm afraid its been cut off, so its hard to tell but one thing to check is if the information that you're after has been included. With github, some information is optional and needs to be ticked to be included in the webhook. Cheers, Simeon.

Hi @Olga Buslovich , could you provide an example of what you're getting? That's the easiest way to figure it out.

Hi @Olga Buslovich, You shouldn't have any issues with that. Webhooks are not authenticated so you'll be able to receive it okay. To try and figure out your smart values, take the advice from @Darryl Lee and log out the webhook data. That will show you everything you can access. Cheers, Simeon.

Hey @John Funk , Afraid I'm on paternity leave till April, sorry mate! 

I'm afraid that the logic that we use in the Email action, "Pending approvers", isn't available as a smart value. The closest you can get is to log out all the approvers and look at their status.

Hey @Mark B Wager I'm afraid it isn't possible with Automation to get the attachment from the incoming webhook and attach it to an issue. I'd definitely try exploring the email sending approach. You can act on issues created that way with Automation. Cheers, Simeon.

@Mark.Stewart I'm from the Automation team so I can tell you that we don't have native support for it and I'm not familiar with the make up of their field but if it is in a fairly normal format then such an approach as suggested will work. Best way to figure it out is to have a look at the REST view of an issue with the…

Hi @Mark.Stewart I'm afraid that this isn't possible at the moment. While it might be possible to set the Team field via Automation, there isn't any means for looking up if that person is in a Team at this time. Cheers, Simeon.

Hi @[deleted] The info panel here is perhaps misleading. There are certain users that the security restrictions stop us from running as altogether. In the case of one of these users we'll fall back to the Automation user when we start executing the rule and that is what the info panel is all about. This is different to the…

Hi @Andrey Boyarin I'm afraid that you won't be able to get the exact list of pending approvers out, however you might be able to log out the Approvers field and then that will hopefully include the state so that you can see which approvers are in pending. Cheers, Simeon.

Hi @Mark B Wager I'm afraid that this isn't possible at the moment. Cheers, Simeon.

You'll need to reach out to the ScriptRunner folks I'm afraid mate. I can't help any further.

Hi @Dalil Chablis, So, if the xray run-time ticket contains the test results in the description or a custom field you could try using the Advanced compare to see if they contain key words that a indicate a test has failed and, if so, create a bug ticket. If not, webhooks would be the way to go. Cheers, Simeon. 

Hi @acc1211, As far as I am aware, this information isn't available out of the box. What did you want to use it for? My suggestion would be to look at addons in the marketplace to see if any of them can provide it where you need it. Cheers, Simeon.

Hi @Dalil Chablis, @Bill Sheboy is right in that Web hooks are a great way to tackle this. When you said "communicate the test results to jira via the Xray api, which generates a test execution" how does this work out? Is the test execution an issue of some particular type or what happens? Cheers, Simeon.

Hey @Dennis Kuiper, @Alexis Robert is right on the money here! This is the correct approach to this issue. Cheers, Simeon.

Hi @Richard Bos , I'll mention the docs discrepancies to the person that maintains our documentation. As for if and when the support will go to server, I have no idea. I'll ask one of their team to update you here. Cheers, Simeon.

Hi @John Funk , I suspect not. This was something we have added since the split and I suspect that the server team has not caught up. Cheers, Simeon.