Simmo Atlassian Team

Hi @Nikki Zavadska _Appfire_, I think for some reason marketplace custom fields behave a bit different, I can't tell you why, so yes, i think you'll have to do it via id rather than value. Cheers, SImeon. 

Hey @Nikki Zavadska _Appfire_ So this is a fun one, but lets see what we can figure out. Its saying cannot deserialize a long out of start object. Translation, I expected a number but got a complicated object. So, for these I think you should try just specifying an id like so: { "fields": { "customfield_xyz": 4 } } Or, if…

Hey @Kevin K, Damn, it looks like it might be doing something weird with that custom field. Any chance that you can raise a support ticket for this? It would make it a lot easier. Cheers, Simeon. 

Hey @Kevin K, No worries, so then where ever you have that create action, add a log action after it. Copy and paste the exact same JSON into the log action and then we can see what it is outputting. If you can paste that into a message inside a code block we might be able to figure out what it is doing. Cheers, Simeon. 

Hi @Kevin K, I've taken your above example and formatted it to what I am trying to suggest: { "fields": { "customfield_12800": {{triggerIssue.customfield_12800}}, "customfield_14703": {{triggerIssue.fields.customfield_14703}}, "customfield_13815": [ { "value": "Web" }, { "value": "Sitecore" }, { "value": "Publish Content -…

Hey @Bill Sheboy Thanks for the shout out re commas! I'll get that addressed! Appreciate it! Cheers, Simeon.

Hi @Nikki Zavadska _Appfire_, The issue is your comma: That comma should only be there if you were going to start another field. There are some good JSON validators on the web that can help with this sort of thing too. Cheers, Simeon.

Hi @Kevin K, did you try copying it in this format: "customfield_12800": {{triggerIssue.customfield_12800}}

Hey @Kevin K, So, your customfield_13815 field looks like: [ { "self": "https://x/rest/api/2/customFieldOption/15207", "value": "Web", "id": "15207", "disabled": false }, { "self": "https://x/rest/api/2/customFieldOption/15717", "value": "Sitecore", "id": "15717", "disabled": false }, { "self":…

Hey @Kevin K, So I'm not sure how you managed to get the multi select cascading select. I couldn't get one setup. But no matter, I'll show you how we get to the answer instead. First of all, we need to see the rest representation of these fields so I can figure out how we get the values you want. For the above issues that…

@Sven Reiser good to know! I wouldn't hold my breathe waiting for that though I'm afraid. But will def keep in mind!

You're talking about changing the behaviour of Jira itself?

Hi @Hein Grebe The approach suggested by @Mathieu Truchot would be the best way to tackle this. Cheers, Simeon.

Hi @Kevin K Could you provide an example of what the data from the trigger issue looks like and we might be able to figure out a smart value. Cheers, Simeon.

Hi @Rob Horan, Could you elaborate a bit more on your use case so I can see if there is anything I can suggest? Cheers, Simeon.

Hey @Sven Reiser and @Bill Sheboy Looks like you guys have dug into this in great depth. Bill is indeed correct that what is being requested isn't possible yet. We were discussing this scenario when implementing the board work but that was out of scope. It is definitely something we were/are thinking about. Cheers, Simmo

Hi @Nirose , You might try forwarding the Tawk.to data to Jira Automation and then using our smart values to extract the data that you need and then create issues with our Create Issue action. I suggest that you look at opening a support case for this as it will be tricky to provide help on this via community. Cheers,…

Hey all, I'm late to the party because of timezones and all of that, looks like there has been some excellent brainstorming going on here. We might have been able to solve this easily with the Lookup issues action but it doesn't support custom fields yet. So I think Bills last suggestion is the best. You'll have to source…

Hi @Soham Das I believe your syntax was initially correct however, you're in data centre. So I'm not sure what the field name should be. If you have a look at: YOUR_SERVER_ADDRESS/rest/api/2/myself You should see all the fields of a user, then follow that structure. It might username in server? Its been awhile since we…

Hi @Christian Bär No worries. We're tracking an improvement for that at https://codebarrel.atlassian.net/browse/AUT-921 Cheers, Simeon.

Hey @Boleslaw Nowak, No worries. So you're pretty close. You want to do the opposite of what you've got: What this is doing is saying, for the issue updated event, was the rank changed. By saying that changelog.Rank isn't empty we're making sure that the rank changed. If you wanted to get more fancy, you could start doing…

Hey @Boleslaw Nowak and @John Funk So you can totally do this hey. You'll need to use an Issue Updated trigger as changing the rank will trigger this event. You can then tell if it is a rank change event by examining the change log with: {{changelog.Rank}} If this gives you something, then the rank was changed. The results…

If you can express the condition in JQL then you can use the above approach with the related issues condition using either all match or some match on your JQL.

No worries, glad it was so easy! :D

Hi @Bohdan Lozinskyi , How do you determine the certain sub tasks?

Hi @Janaki.R Sorry about the delay. I've had a few big days of dealing with support escalations and I'm just catching up on things now. I think the best cause in your new rule would be to use the Delete Issue links action to delete your existing link, then do the linking to the new issue. Would this work? You can delete…

Hi @Petr Sigaev, No worries mate! Glad we got there in the end. I do apologise for taking so long to realise what was going on. Glad it works! Have a good one. Cheers, Simmo.

Hey folks. So, the answer is that it depends on who the rule is running as. If the rule actor is set to our user "Automation for Jira" then it shouldn't need to be on the screen as that user has some extra permissions that allow it to bypass the screen check. However, if the user has been changed to someone else, then it…

Hi @Petr Sigaev, My apologies mate. I'd forgotten that team managed projects had introduced the People field, which we don't currently support in the UI. We should be able to get the JSON going here. The underlying field structure is a list/array. I just spent a bit of time on my dev instance figuring out a smart value for…

Hi @Petr Sigaev Is your field a cascading select?