Darryl Lee Community Champion

So I asked around and a bug was filed yesterday: https://jira.atlassian.com/browse/AUTO-892 But later last night it was Closed as Not a bug. But um, I still don't see Sprint actions. Anybody else? OH DANG - they removed the Sprint actions from the documentation:…

Hi @Bill Sheboy - I just upgraded one of our test sites to Premium, and don't see Sprint there either. Oh hey, maybe they're trying to turn it into another feature that's only available to Enterprise. :-P

For simple canned messages, Client Notifications is probably preferable, as it is much easier to manage.

Glad we got it working!

So Cloud Enterprise, which provides for "Unlimited" instances of Jira/Confluence/JSM is the only tier that prevents rogue instances from being spun up, whereas Atlassian doesn't provide this mechanism to users paying per instance on Premium? Thanks a lot.

I think see the problem now. For the Header name you wrote: Authorize It should be: Authorization Give that a try!

Hey yeah, no, that's definitely a problem with the Authentication token. You followed these steps: * Set up a Personal Access Token * Your Authorization header will be: Bearer <yourToken> * Reminder, you DO NOT need to base64 encode your username:token. That is only on Cloud. I would delete the old token, regenerate a new…

Aw bummer. Yeah, that makes sense.

GAH, I had a typo in the URL (last parentheses was in the wrong place). I've fixed it above, and here it is, corrected: https://YOURJIRASERVER/rest/api/2/user?username={{issue.comment.last.body.match("\[\~(.+?)\]").first.urlEncode|issue.comment.last.body.match("\[\~(.+?)\]").urlEncode}} Sorry about that. I added urlEncode…

Hey Quang - is your username in Jira not also quang.nguyen2? By Username I mean what you see at https://YOURJIRAINSTANCE/secure/ViewProfile.jspa

Ahhhh, @Kalyan Sattaluri and @Bill Sheboy's discussion above made me realize there's possibly a much simpler solution. IF your JIRA usernames are the same as the first part of your company's email addresses (which is fairly common, especially if you sync with Active Directory for your accounts), then you wouldn't need a…

Oof. I'm sorry to hear that leadership made such a poor decision. But hey, one bad idea deserves another right? So let's get hacking! Regex Ok, so the regex you want is this: {{issue.comment.last.body.match("\[\~(.+?)\]").first|issue.comment.last.body.match("\[\~(.+?)\]")}} (A great resource for writing and testing regular…

Hi @John Maner - I don't think there is a .keys function for Lookup Tables. That would be pretty sweet. Instead, I'm thinking you'll have to make a smart value variable with your keys (flavor-1,flavor-2...), and then use .split(",") to iterate through them. Ah yeah, this seemed to work: NOW, before you kill yourself trying…

I'm not sure how this would work, because when I type @ darryl to mention myself in a comment, it converts that to: [~darryllee], which is NOT an email address. Are you saying that users have been trained (and are willing?!) to @ mention someone with @ darryl and then also type darryllee@youremail.host? So a comment would…

So I looked at the changelog API endpoint and I think it might have what we'd need. When 4 min is up, you'd need to do a web request to: https://YOURSITE.atlassian.net/rest/api/3/issue/{issueIdOrKey}/changelog?maxResults=100 (You will want to tune that # to balance the max number of changes to a ticket vs load time for the…

Doh. You're absolutely right. It'll send two messages. I THINK maybe you need to do another check to see if there have been more than one changes to the Status Update field in the last 4 minutes, and if so then do NOT add a comment. I wonder if this is possible by hitting the issue history API... I'm typing on my phone.…

OUCH!

So there's a hack that I've used before, making a web request to an external website: https://hub.dummyapis.com/delay?seconds=3 (It turns out I was not the first person to come up with this workaround: AUTO-238) The caution is that there is a 5 minute maximum execution time for automation rules: * Automation service limits…

Glad it is working! By extra comma, I meant that if your test for TEST fails, then the last element in fields before the closing braces would look like: "customfield_10103" : { "id": "{{environment.get(issue.customfield_10266.id)}}"}, } } And so there's that extra trailing comma. But I guess Automation doesn't mind that.…

So what finally worked? Adding the # and removing braces, per my example? OH, if it is still not working, I see another issue. You end up with an extra comma if the TEST fails. I think you can probably put that comma from the line above (after customfield_10103) before the customfield_10014.

Hi @Srinivsarao Mutyam - this is a signficantly different question and I'd be happy to answer it if you can create it as a separate post.

Ah, yeah, it's weird how sometimes the documentation shows if with a # and other times it does not (even outside of the list context), like here for the exists function: {{#if(exists(issue.designer))}}The designer for this issue is {{issue.designer.displayName}}{{/}} But yeah, then I guess the real problem in your case was…

OH! I found the issueUpdates you were talking about. It's part of: * Jira Cloud platform / Reference / REST API -> Bulk create issue That's cool! Unfortunately that is a different API call than what I think Automation gives us access to, which is the only as part of an issue Update/Edit. So only these options would apply:…

Hi @David Leal! I think there's a few issues. * You're missing a # mark before the if * You don't need to put userInputs.team in {{braces}} because you're already inside of a function that works with Smart values. So I think what you want is: { "fields": { {{#if(equals(userInputs.team, "TEST"))}}"customfield _10014":…

I don't believe you can create subtasks via JSON. You probably will need a second rule to create the subtasks. Here is a good solution describing this: * Clone Epic, Stories and Subtasks tree with Jira Automation 

Hi @Andrei Margarint - I was wondering if you had a chance to give this a try, or had any questions.

Hi @Raphael Fernandes -- The Labels field has a handy ADDREMOVE option that lets you do exactly what you want:

Bizarre. The custom smart variable the first time around is 24 assignees. So you started getting the error when you added another Lookup for: project = 11844 AND type="finding" AND resolution is empty AND assignee={{distinctAssignee}} So like, 24 times, it should run that query and each time it should return a set of…

OH SHOOT, there is a distinct. Nice! Huh. That is a weird error. When you say you had a small amount of assignees, do you mean you scoped the first Lookup to only include certain assignees? I guess first off, how many issues are we talking about in the original query? And how many distinct assignees are there? (You could…

Hi @Philippe Lassalle - can you post what you've tried, and what errors you may have gotten? Are you getting the same error as @Stefan Salzl? Operation value must be a string (labels) The problem was Stefan was trying to basically do: "add" : "Label1, Label2" From the documentation, when you use add for labels (notably if…