Darryl Lee Community Champion

So, I missed checking in Tuesday and Wednesday, because here in the U.S., a different annoying thing was happening. But I'm BACK, and oh boy. We had ONE day (Nov 5) before yet again two new sites were mistakenly created yesterday. Welp, at least I don't have to update the image.

Here's the "collapsed" version of the GraphQL call, with all the other bits I used in curl: curl 'https://YOURHOST.atlassian.net/rest/gira/1/?operation=issueViewRemoteDataQuery' \ -s -n \ -H 'content-type: application/json' \ --data-raw $'{"query":"\\n query issueViewRemoteDataQuery($issueKey: String\u0021) {\\n…

Ok, so I found some endpoints, but ugh, yeah, it's unofficial and undocumented, and WORSE STILL, it's GraphQL (nooooooo!) ⚠️ Use of Unofficial and Undocumented APIs is NOT RECOMMENDED for any production tasks or Automations. This information is strictly for informational, and possible one-time uses/runs/migrations etc.…

Hum. Worth a separate article, methinks: * What's another word for blackmail? 

A few questions: * Is this compatible with Azure AD for nested groups? * If we've switched from SCIM to Azure AD for nested groups, is this functionality unavailable to us? * Does this synchronization allow us to BLOCK users from creating their own teams? Or at least teams with the same name (which is inexplicably…

Ha "My head has been in the cloud for too long" (Matt explaining why he doesn't know about new Data Center features)

I think we might just do a Page Include of our existing Intranet space's home page for our Company Hub. :-}

Oh no, too late?

Oh shoot. I forgot to check over the weekend. Zero created Saturday or Sunday, but come Monday... nope. ANOTHER SITE CREATED BY ACCIDENT today! So the count remains ZERO again!

via GIPHY Ugh yeah, it's infuriating that without Guard, you can't do anything about these sites. And these emails that notify you about them without actually TELLING who created it or what the site URL is are infuriating. It's does feel a bit like a hostage/blackmail situation: TAKEN (ADVANTAGE OF) based on true events…

Gah, I posted too early! Back to ZERO. And this was entirely predictable - It's been two days since the expedited deletion request finally went through for roku-team.atlassian.net, which is the site name that Atlassian's broken login/signup workflow suggests for users. It certainly would "look" right to a user just trying…

Ohai. Yeah, I took a look at the Lookup action and ugh, as @Robert Klohr and @Shawn Doyle - ReleaseTEAM correctly pointed out back in January and May, the "Lookup Pages" feature does NOT support CQL, despite what @Avinoam wrote in the original post: New Lookup Pages Action What is this component? Similarly to the Lookup…

Glad it worked, and ooof, yes, it should be parent, not parentEpic, as John and @Trudy P Claspill pointed out. I've corrected my answer.

Hi @Esteban Halabi - I think @John Funk answered something similar here back in May: * Help Needed: Automation Rule to Sum Child Issues' Fields and Update Epic He got the average of children's fields, instead of sum: You'll need to adjust your Lookup JQL to: parent = {{triggerIssue.parent.key}} And you then Edit your…

Ah, newlines. A good thought, and I recently discovered that Automation's regex supposedly supports multiline and single-line modes from Java's Pattern class. So for good measure I tried adding (?s) which should enable DOTALL mode which means the . will match line terminators (which includes newlines). But my regex is…

Ah thanks @Kieren _SmolSoftware_ - yeah, now that I think about it Vortex does sound vaguely familiar. I think somebody I chatted with in Barcelona may have mentioned it. Ah, the new user management experience introduced in 2021 that our Org still doesn't have access to. :-} (Too many users? Multiple product sites, ... I…

Ooof, speaking of .size, I was recently working on a rule trying to find the # of @mentions in a comment. (I actually wanted to go through all the @mentions to see if one or all of them are internal addresses, which we've looked into before, but alas, I could not figure out how to concatenate all the addresses together…

I have another suggestion I will be adding to CLOUD-12089. Since it's highly unlikely Atlassian is going to add a new Cancellation reason that would acknowledge their broken login workflow that causes accidental site creations, what if we all agreed upon a hashtag that Atlassian could easily search on? #shadowit ?…

Ugh, as usual, my rubber-ducking forced me to do a better search through docs and I found it: Default values If a field or value doesn't exist, it usually returns an empty value, such as {{invalid reference}}. If you need to have a value, you can specify a default value. For example, when an "invalid reference" doesn't…

Sorry, this is totally a necropost. But I was curious @Bill Sheboy, how did you figure out/discover: * the default value operator pipe |, such as with {{issue.Story points|0}} I couldn't find this (of course) in Atlassian's official docs... And I'm poking around the source for mustache.js and mustache.java but am not…

Hi @Philip Kroos - TEAM XALT - I'm wondering if you could add an IF block that checks if {{triggerIssue.fields.customfield_10633}} is EMPTY before it even attempts to do the Edit.

Hi @Dave Fleming - as far as Atlassian the discount is 75% off for cloud subscriptions, and they offer free product coaching and some consultation sessions: * Atlassian for Nonprofits [If you have a spare server lying around (or AWS/GCP credit) and technical expertise to maintain it, you could also get free self-managed…

Dude. This is very very slick. That is all. :-O

OR, I'm an idiot and didn't read the docs I quoted: "customfield_11449" : { "id": 10112 } You don't need quotes around the option ID. So you want this: "customfield_10632": { "id": {{#if(equals(triggerIssue.fields.customfield_10633.id, "11392"))}}11390{{/}}{{#if(equals(triggerIssue.fields.customfield_10633.id,…

@Bill Sheboy speaks the truth about nested double-quotes. I missed that. And yes, screenshots would helpful here. ALSO helpful: Audit logs. You can put the full expression into an Audit log, but you also should put pieces of it, like: {{triggerIssue.fields.customfield_10633.id}} and…

Oh yeah, and folks are not happy about here either: * An update on product requests: bringing shadow IT controls to Trello and Bitbucket 

It's not a great solution, but you can add Audit Log messages (which have the added benefit of helping with debugging). Another option might be to Create Variables that are just used as labels/comments? Neither of these are exactly right, I realize.