Simmo Atlassian Team

Hi @pe , So they should be there however, custom fields for team managed projects are specific to that project. So it depends on where you're configuring your rule. If you're in another project it won't show up. It will only show up in that project and global / multi project rules. If that isn't the case, please raise a…

Hey @Rudy Holtkamp, Noted :) I've pointed it out to our PM. What you described is not to dissimilar to other features we've discussed. Cheers mate. 

As far as I'm aware, we haven't changed anything in Automation that would have affected this!

Hey @Rudy Holtkamp I'm afraid that we're not at the level of Automating ourselves yet! :D So I'm afraid you won't be able to copy Automation rules from Automation rules.

Hey @A_ Ethan Vaughan What sort of things would you like to do with the Request Type Groups? Cheers, Simeon.

Hi @Petr Sigaev When you say that it is a multi user field and it isn't showing up, is that in the list of fields to edit for the Edit Issue action? As far as I can see in the code we support multi user fields and it should be showing up. If you look at the JSON response as mentioned above, is the field type…

Hi @Janaki.R You can achieve this with Automation easily. I've just put together an example of this for you: This is assuming you're using Fix Version but you can do it with any field. Cheers, Simeon.

@Kautilya Fadia IN , try changing the ### to a single # That seemed to work for me

Hi @David Loszewski, I'm afraid that at this time, Automation doesn't have any inter instance capabilities at the moment. Cheers, Simeon.

Hi @Christian Bär I'm from the Cloud team, not the Server team. However, what I can see what the issue most likely is. We haven't exposed the ability to access the colorName field, only the name and key are accessible at the moment. I'm afraid that this is beyond my control. I suggest that you open a support case and see…

Hi @Christian Bär , Just wanting to clarify that I understand what you're asking. You're wanting to send an email to everyone in a particular organisation? Cheers, Simeon.

Hi @Kautilya Fadia IN , If you could attach some screenshots of how you're generating the URL in the automation rule that would really help. Cheers, Simeon.

Hi @Bill Sheboy I've pinged them again.

Hey @Darryl Lee, that isn't something I can answer I'm afraid. However, I've pinged the server team and asked them to provide you an answer :)

@Brian Eschen , the description of AUT-247 does have a suggested work around if that helps at all.

Hey @Bill Sheboy, Can you run the edit variable action past me? Whats the use case here? In terms of the lookup supporting all fields, the reason why it only supports what it does currently is performance. There are some fields that aren't part of the issue or that we need to fetch additional data from Jira for it to make…

Hey @Omer Joffe (MG) Can you raise a support ticket for this? You're doing the exact same thing that I am able to do successfully so I am not sure what is going on here. We'll need to dig into the problem to find out. Cheers, Simeon.

Hi @Omer Joffe (MG) In this case, the error is happening with the add customer action. A customer already exists with that email address, so we don't create one so the smart value doesn't work. Looks like you're testing this so try it with made up emails. Cheers, Simeon.

Hi @Omer Joffe (MG) , Could you share a screenshot of your rule setup and where you're stuck?

Hi @fabila , Yep, it should. Think of it as a "refresh". Put it before the action that is having the issue so it can refresh it. At the end of the rule nothing else comes after it so isn't getting the benefit of the refresh.

Hi @Ulrika Eriksson, I didn't realise that you were on server. You should have the Value Changed Trigger available. Are you on the latest version? Cheers, Simeon.

@Ulrika Eriksson the approach suggested by Bill is the way to go. Let us know if you run into any issues.

Oh gotcha, but in Jira you can add a project role as a watcher?

Hey all, @John Funk, it would I believe. @[deleted] that suggestion by John is probably your best bet. We unfortunately don't have any way to trigger rules when someone is added to a role. I suspect that there isn't an event from Jira for this so there is no way we'd be able to do.

Hi @[deleted] So, if I read this correctly you'd like a trigger for one when someone is added to a role in Jira? Cheers, Simeon.

Hi @Alexey Paveliev Ah, I see your issue in the first screenshot. So, the smart value you should be using is just: {{issue.summary}} The reason for this is that issue refers to whatever issue is in context. In your case, you haven't used a branch at all and your trigger is issue transitioned so that is the issue in…

Hi @Gerardo Dalena Ultimately, I think you need one of our backlog items https://codebarrel.atlassian.net/browse/AUT-1241 which would allow you to filter items out of a list. That might make things easier here. However, I'm afraid that, yes, you'll need all the combinations. Or, a custom field. If you had a field you could…

Hi @tal It looks like you still have the yes wrapped in double quotes in your advanced compare?

Hi @Alexey Paveliev Can you share some screenshots of the rule configuration? I'm still a bit confused as to why you can't do that. You can using smart values. What sort of project is it?

Hi @[deleted] I'd like to see if I can help but I don't quite follow your scenario. Could you outline it for me in a bit more detail please? Cheers, Simeon.