Heather Ronnebeck Community Champion

Ok so I've tried that. It didn't make any difference when I tried to run it again. The exact same error came up. 

Ah, thank you. I'll give that a go. I thought that it was only used for actual exports and not automations.

This is the same issue I am running into. 

Thank you @Bill Sheboy !!! That's exactly what I needed. I kept doing latest instead of last which was what was throwing me off. 

Here is the rule in it's full working glory before this requirement. What I found is that the Web Responses were pulling in more than one ios and more than one tvos fix version now that is unreleased. 

And now this story has another chapter..... So we've been running this rule for a week, and found a hiccup with it. It appears that they actually don't have just 2 versions (1 for each), so we need the automation to pull in the latest version created that starts with either ios or tvos. So what I've been trying to do…

I got it!!! It works!! So what I needed to do was add a few re-fetchs in there and then also make sure I checked off the checkbox for: Delay execution of subsequent rule actions until we've received a response for this web request The part that I was stumbling on before you last update @Darryl Lee was the add vs replace.…

More like: * IF iOS * WebRequest to get iOS version * ADD version to fixVersions (instead of current REPLACE) * IF tvOS* WebRequest to get tvOS version * ADD version to fixVersions (instead of current REPLACE) * ELSE* WebRequest to get iOS version * ADD version to fixVersions (instead of current REPLACE) * WebRequest to…

@Darryl Lee and @Bill Sheboy Thank you so much for the help. It has gotten me 95% of the way there, now there's one last kink in my automation which is the scenario of when there are both tvOS and iOS in the field and both versions need to be mapped into the field. I have tried using…

I think we got it. This is the final rule for anyone else that needs it. Thank you so much @Bill Sheboy and @Andrea Robbins 

@Andrea Robbins I noticed that you have other steps in the automation branch that aren't in your screenshot. Am I missing other steps? I am getting new errors now. Now we can't find the release version at all.

@Bill Sheboy @Andrea Robbins Here's the rule in its current state. I hope this helps. I haven't touched it since we last spoke.

Hey @Bill Sheboy I'm just traveling right now from Team so I haven't had a chance to look at this again in a while. As soon as I can I'll post the automation and we can continue working on it. Thank you again!

Hey @Andrea Robbins I did the updates you're suggesting, but I am still getting the error that the provided smart value couldn't be resolved to be an object. I think I'm doing something wrong at the Branching step. 

The format you provided did help a bit, but the error I got was "The provided smart value couldn't be resolved to an object"

I was trying to pull out when there were two fix versions vs one in the rule. This is for a single project scope. 

Hey, The issue I'm running into is that it's not having a good time pulling out those fix versions. It seems to not be able to make it an object. 

@Moritz Lindenau , It is still the best way that I know of doing this. I did speak with their team, but haven't heard of any updates on how to do this any better. 

I would also add that for the Regex part. The word Empty won't work as Regex is very specific. I'd leave it blank and change the second field to to be that it does match the regex. 

Hey, Have you taken a look at this doc? https://support.atlassian.com/jira-service-management-cloud/docs/access-smart-values-for-forms-and-form-fields/ From what I can see, you might need to do something like {{forms.last.c4p4-brand}} or potentially {{forms.last.c4p4-brand.label}} I hope this helps a bit.

Are there plans to introduce security on the components where only some individuals can see the component options selected? I have a use case where the Compass components are internal only, but external users can currently access the tickets and see them. 

Hi Andy, Thank you for sharing your post with the community. Setting up a PMO within Jira itself is fairly simple on the tooling side. The challenge is actually within how you want to structure your team, and the projects they are managing. You also have to consider other factors like: * the other teams you're interacting…

Hi Andy, That is correct. The Problem Management module in your JSM project is designed to do just that. You may have to modify the workflow to make it work for your team, but out of the box that feature set in the project settings should give you what you need to tackle that first problem out of the gate. I hope this…

Please feel free to email me here.

These are some great resources for self paced learning. 

@Nicole Jones-Campbell I can offer some instructor led training to you as an authorized instructor. If you're interested we can look at doing something this month. I might be able to make next week work depending on how the availability lines up. As @Elena Lurye also mentioned, there are several partners out there can…

Hi @Nicole Jones-Campbell , Are you looking for a virtual class that is self paced or instructor led?

Alright... I think I answered my own issue. I'll post it here though. It looks like when doing an automation like this, you want to do 2 things. 1. Use {{issue.fieldname}} not {{issue.parent.fieldname}} in the Create Issue action I mentioned in Step 3.1. 2. Make sure in the same create issue action in Step 3.1 you have the…

I'll give it a go, but just looking at the first API doc I can say it looks like jibberish to me. I'll try to figure it out. Thank you.

Working Agreements While we are working on the never ending changes that take place in our environments, I think this is a good play for our group to use just to get everyone on the same page with how the team works. It's one that I've ran before, but like the course says, it can be ran multiple times for any reason. I…