Simmo Atlassian Team

Hey @John Funk , Multi value fields and value change is a bit of a tricky one. We've got: https://codebarrel.atlassian.net/browse/AUT-2013 and https://jira.atlassian.com/browse/JRACLOUD-74953 The issue here is the way that the changelog treats the value change we get two entries I think. One for the old value and one for…

Hi @Tobias Magnus (ext) , That's roughly the right approach and should work if there is only one sprint set. You don't have a lot of options when it comes to multiple sprints and trying to find the active one, so if that works, go with it! Cheers, Simeon.

Hi @Tobias Magnus (ext) , So, this is a bit more tricky than it looks. When you say sprint number, are you referring to a number in the name of a sprint? As a sprint doesn't have a number field indicating which it is. So, the first problem to solve is how to get the number of a sprint. The second problem is that an issue…

Hi @george_hatzopoulos , @Jack Brickey is pretty much on the money for how to tackle this! Cheers, Simeon.

Alright, @Ian Robinson & @John Funk aka Funkmaster! What a curly one. You've no idea how hard this was. It is very hard to get the fields that were removed and the fields that were added out of the Field Value changed trigger because we're dealing with a multi select so its sets of values. The approach I took was: whenever…

Hey @Ian Robinson & @John Funk , This is more tricky than it seems. I've been playing with a few ideas. Just waiting for a team member to be back tomorrow to see if it is possible. Cheers, Simeon.

Hey @Ian Robinson , It may be possible. It depends on what you want to do with that list and what event you want to trigger it? Cheers, Simeon.

Hi @Caio Fernandes , I'm afraid that there isn't really any easy way to do this at the moment. We have an item in our backlog, https://community.atlassian.com/t5/Automation-questions/Sprint-end-date/qaq-p/1467444 which would help with this. In the meantime, you might try Florian's workaround. Cheers, Simeon.

Hi @Alexey , You can find of some in our docs at https://support.atlassian.com/jira-software-cloud/docs/advance-your-rules-with-smart-values/ Otherwise, the other way to view the options is to look at the REST representation of an issue and see what is there! Cheers, Simeon.

Hi @Alexey You should be able to get this to work if you adjust your smart values to reference the email property: * Reporter {{issue.fields.Reporter.emailAddress}} * Creator {{issue.fields.creator.emailAddress}} User fields by default just reference the account ID if no property is included, which is what you are seeing…

Hi @JMP Support , Thanks for your question. I'm going to need a bit more background information so that I can help you out. How are you cloning Story A -> Story B? Is it with an Automation rule? If so, could you please attach some screenshots? Cheers, Simeon.

Hey @Sam Sexson , Sorry about the delay in getting back to you. So, what I think is going on here is that schedule is an array/list. So, webhookResponse.body.schedules and .schedule are both referring to a list. When that happens, we apply whatever comes next to all the list elements. In your case that…

What Stephen said :)

Hi @Sam Sexson , Could you provide an example of the web hook payload for me (remove anything thats PII or company related). Would make it a bit easier to see what is going on. Cheers, Simmo

Hey @Bill Sheboy , With the other one that you saw, was it also issue created? If so, they might need to add a refetch action to the rule. Occasionally we can get an issue from Jira that was created but the epic has yet to be set on it and a refetch can often sort that out. Cheers, Simeon.

Hi @Evan , The advice that Bill gave you is correct. I would have a guess that the issue that failed your rule wasn't a sub task and so we couldn't find the parent issue because there wasn't one. The best thing to do here is to add an issue condition that checks it is a sub task before trying to edit. Like so: Cheers,…

Hi @Ivan X , If you're using Automation for Jira then it would be [~{{issue.assignee}}] however since you're using built in Automation I'm afraid I don't know what the answer is there. Cheers, Simeon.

Oh, sorry, my bad. I just realised that you're on server. The accountid: part is cloud only. You should be using [~xxxx] where xxxx is the user key.

Hi @Ivan X , @Rudy Holtkamp is correct re Automation for Jira. They look right. There's more in ours docs about it, https://support.atlassian.com/jira-software-cloud/docs/convert-usernames-to-user-account-i-ds/ Basically, it should always be: [~accountid:xxxxxxxxxx] where xxxxx is your smart value.

So it sounds like the smart value is not getting the correct value out of customfield_15070. Could you look at the rest representation of an issue with it set and provide the details of it? Eg https://xxxxx.atlassian.net/rest/api/2/issue/BIO-14?expand=schema would get the rest representation for bio-14. You're then looking…

Hi @Lukas Pieger , I'm afraid that you can't do this through Automation. I had a quick look at service desk's rest API (https://developer.atlassian.com/cloud/jira/service-desk/rest/) but I don't think that they support that either! Sorry! Cheers, Simeon.

Hi @Lukas Pieger , If you're talking about avoiding creating customer accounts for a service desk project it might be possible through Automation. You could create a rule that is triggered by an Incoming webhook, sent from your service and including their details, then use the Create Service Desk Customer action to…

Hey @Ivan Wilson , @Gikku is correct in their answer. Jira Automation has such an action. You might be getting it confused with Service Desk's internal Automation however?

@Breonna Bowen , could you post a few screenshots of the rule as well so I can get the context of how it is looking now?

And use a default value for when the field is empty. So taking the above suggestions, it would look something like: {{#=}}{{issue.time waiting for submitter (days).value|0}} + <your calculation> {{/}} I added the |0 which will default to zero if the field is empty. If you don't do that then you'll get an expression error.

Hi @Teza , You can do this with the Automation for Jira addon as well. It is really easy to put together a rule that would do this. For example: This rule will create a ticket in another project when a ticket with a component of Support Question is created in another project. Cheers, Simeon

No worries guys, glad it worked :D Unfortunately, its got to be Gluten Free Beer now, that lessens my chances! :D

Hi Rick, I'd have a crack at what Bill has suggested, it sounds like a sound approach! Cheers, Simeon.

Hey chaps, So, you should just be able to reference the field in the minus part, eg: {{triggerIssue.duedate.minusDays(issue.Custom Number Field)}} Let me know if that doesn't work for you, it should.Cheers,Simeon[Automation for Jira - Dev]

Hi @Jaroslaw Wojciechowski , I'm afraid that I don't have an ETA for you at the moment. Cheers, Simeon.