Darryl Lee Community Champion

Hey Stephen - yes, you're definitely running into an order of operations thing. Namely: AUT-517 - Rule branch order is non-deterministic. In some cases it would be better for branches to execute in order. But I'm also a little confused by your rule. You want to set all Sub-tasks to Done, but if any were not Done (prior to…

It's a little ugly, but I think you could do a Web Request to get this. You'd need to take your {{pullRequest.url}} and use some text manipulations to change it into the appropriate API call (depends on your Git server - you'd also have to set up a service account/token etc etc). For Bitbucket Server, this seemed to work:…

When I was younger, and worked at an old-school Silicon Valley hardware manufacturer with an old-school break room with old-school vending machines, it would be Coke or Mountain Dew. And maybe to round it out, a Snickers bar. Fast forward 20 years, and I was fortunate to work at two of the FANG companies where healthy (and…

Thanks @Daniel Eads I just signed up to take a look. Since I had to join their community, maybe I'll ask there about the possibility of expanding the data that is available when Downloading Your Community Content.

Oh wow, according to the Liftblog (because of course, the Internet), "this chairlift [the old Skyride] at the Oakland Zoo only operates at peak times." https://liftblog.com/skyride-oakland-zoo-ca/ And indeed, the Oakland Zoo's map only lists the Sky Ride as "temporarily closed". https://www.oaklandzoo.org/map So hey, you…

In 2018 they replaced those scary open-air chairs with enclosed gondolas - made by a fancy Swiss ski-lift company. https://www.oaklandzoo.org/blog/gondola They look soooo much safer. OTOH, I'm glad I got to experience that 70s-style laissez-faire approach to safety one last time. And that we survived. :-} Oh, I guess if…

Hi Doug - yes, that looks right to me. By the way, I always test my rules by using a Manual Trigger that is only visible to me (administrator or site-admin group, for instance.) https://support.atlassian.com/jira-software-cloud/docs/manually-run-a-rule-against-an-issue/ Then I can create a single test issue, add all the…

Yes, "multi" needs to be replaced with the name of your custom field. If it has spaces, you would use: {{#issue."Your Custom Field Name"}}"{{.}}"{{^last}},{{/}}{{/}} And in some cases, that format doesn't always work either, so you might need to use: {{#issue.customfield_10034}}"{{.}}"{{^last}},{{/}}{{/}} There's several…

Screenshot: https://photos.app.goo.gl/Zog8u8uEq3sqAmwj6

Hi! You can do this iterating through all of the multi-select values as a list and using advanced field editing to update them. Here's what I tested putting into Additional fields, where my multi-select field is named "multi": { "fields": { "labels": [ {{#issue.multi}}"{{.}}"{{^last}},{{/}}{{/}} ] } } I'm not sure why I…

I've started a few discussion threads in case people (cannot|prefer not to) Google Docs: * Confluence - Discussion of Functional Differences between DC/Server vs Cloud * Jira - Discussion of Functional Differences between DC/Server vs Cloud 

If you're averse to Google Docs, please feel free to add your additions for Confluence here, and I'll see about adding them to the sheet.

Ok, I've created some very rough tables for people to contribute to: * Jira Server vs Cloud - Functional Differences * Confluence DC/Server vs Cloud - Functional Differences Basically I did a quick copy/paste of the existing KB articles (referenced in the Notes column), and tried to boil things down to a binary yes/no for…

There's a huge need for side-by-side comparisons of DC/Server vs Cloud features/usage. I think maybe I'll start a collaborative doc for this.

Oooh, free book to add to my stack. Thanks!

Ha, like others I'd never seen this feature either, so look forward to seeing it soon.

I wonder if the software behind the Atlassian Community might ever be released as a product. Or Open Sourced? :-}

Congrats all - I recently ticked past 30 answers (I *think* they're all in cloud, but w/o metadata in JSON, it's hard to tell. :-), so I'm anxiously looking forward to getting a Cloudie of my own.

I appreciate videos like this and the other ones you've been posting. They'll be a handy resource to provide for folks that don't need or have time for a full training session. 

This is a new feature? I could've sworn I saw some requests like this months ago? Maybe we were getting a preview?

This is interesting. I was reminded of recent post about being able to require Time Tracking for certain users which would require a separate Issue Type for different user groups. Maybe this approach could be adapted to that - have a "catchall" Request Type, and then use Automation to route it accordingly, post-creation.…

I wouldn't mind more data, but along with it I'd like some preset filters to deal with the additional data.

If your only parent type is Epic, I believe that should work. Are there any additional constraints? Is it only *you* that should be receiving emails? Or maybe the current Epic assignee? If you wanted that, you could add {{issue.parent.assignee}} to the list of recipients. Also, it might be nice to have a link in the email…

The only way I was able to get the Previous assignee to show up in a Comment (or the log) was to add the Assignee field to the screen used in the Completed transition, and then change the assignee. But at any rate, it looks like Automation is not properly interpreting Smart Values inside of the brackets, so the @ mention…

Hey Dylan - can you please send a screenshot of your rule? I've repeatedly been unable to get either the accountID or displayname of the Previous Assignee using any of the code you posted: {{#changelog.assignee}}{{fromString}}{{/}} OR {{#changelog.assignee}}{{from}}{{/}} What I'm wondering is whether in fact, you're not…

As for figuring out fields for JQL, the easiest way to do that is to open up a Search in another window, where you can toggle between Basic/Advanced, and also take advantage of auto-completion: https://confluence.atlassian.com/jirasoftwareserver/advanced-searching-939938733.html Then when you have the query you want,…

So {{issue.key}} will select the subtask because the Branch rule is processing subtasks, and so that's what the issue.key refers to. If you also wanted to include the Epic number, you could do: This issue is a blocker for this Epic: {{issue.parent.key}} And if you wanted those issue keys linked: <a…

I just tried using {{#changelog.assignee}}, and it only worked if the assignee had changed as part of whatever triggered the rule. I don't see an assignment change in Dylan's original rule, so I too was wondering how they were able to get that value.

Thanks. That looks right to me, so I'm not sure what the problem is. One thing I might try is to add some Audit Log actions to be double-sure you're getting to certain points in the rule AND to validate the Smart Value output.

That simpler rule would look like this: