Darryl Lee Community Champion

FYI it's way down at the bottom of https://YOURSITE.atlassian.net/jira/settings/system/general-configuration :

If this was a question, my answer would be, no, I don't like this new feature. Thankfully Atlassian appears to FINALLY rolling out a feature to let you turn it off, site-wide: We apparently received it on our Sandbox that is on Preview Track on Feb 9, but it is not yet on our Bundled Track production server. It shows a…

FYI the setting is very easy to miss way down at the bottom of Jira -> Settings -> System:

Ohey everyone. It looks like this finally rolled out, or is rolling out. We apparently received it on our Sandbox that is on Preview Track on Feb 9, but it is not yet on our Bundled Track production server. It shows a Rollout schedule of Feb 9 - Mar 9, which I will point out does NOT align with the "second Tuesday of each…

OH wow, I was not familiar with this add-on that Trudy mentioned, nor have I used it, but it appears to be built for this one thing, the reviews are solid, and it's pretty cheap: Default Values for 'Create Issue' screen - Issue Templates 

Ahh, @Trudy P Claspill answered this far better than me last year: * How to add a standard text in the description field when creating new task Notably, she points out: If you are using a Team Managed project, you can set a default value for the Description field, and that value will show when you are in the Create dialog.…

Ok, I forgot that a long-standing workaround is to create a "Custom Description" field and display that field (instead of the "real" Description field) on the Create screen with default text, and then using Automation or a Post-Function, copy the value of that field to the "real" Description and hide the "Custom…

Ah, so what you're talking about now is a template, or default text. Ideally you'd want your text to show up as soon as somebody clicks [Create]. The Automation I gave you will simply append it to whatever they already entered into the Description. This is a long-standing problem with Jira - they let you set default text…

Hi @Timi Falusi - yes you can accomplish this with the use of Smart Values! Here's what that would look like: You can also use Smart Values for other fields, once you Choose them from the drop down.

SIDENOTE: @Haddon Fisher I love your site name, and your mission statement: I will be digging deeply into Jiramancy very soon!

Thanks @Bill Sheboy - this actually led me to a workaround from having to make a Web Request to lookup project ID, by way of @Haddon Fisher's solution of setting the project in the "Additional Fields" JSON. As he writes: Ticket Creation Use "same project" value in the "Create Issue" action and then use the following JSON…

Official post: New feature: Compact Mode and Max Width to support information-dense documentation 

Sounds like this is a known issue? Was it mentioned in a previous answer? Of course Atlassian doesn't have documentation, and the error message specifically says: Specify a valid project ID or key (project) Grrr...

@Barbara Szczesniak @Stefan Vollmer If anyone said anything about a per user setting, it wasn't me. The Compact setting appears to be page-specific, and as @Keith Furnell observed, it seems to be automatically applied when Legacy pages get converted to New Pages. (Which makes sense since it the feature appears to have been…

Gah. It seems that I can't use a Space KEY in Clone work item. I have passing in the {{parentKey}} and I'm extracting parentSpace thusly: {{parentKey.split("-").first}} And Audit Log shows: parentSpace: ITTEST Clone work item lets me use a Smart value - cool cool cool. But then I get this error: Unable to create work item…

Oh my gosh, I didn't even consider that {{^first}} could be used to lop off the first element, duh. Couldn't you avoid the trailing comma with the old {{^last}},{{/}} trick? (One of the few things Atlassian actually documents?) Let's see! Ah yeah, this is much cleaner (albeit a bit more cryptic than my original solution)…

Oh oh, I got it: thisChildRegex = {{thisChild}},? (Where ,* means 0 or 1 commas.) And then: remainingChildren = {{childArray.replaceAll(thisChildRegex,"")}}

Oh god. World's jankiest solution: childComma = {{thisChild}}, And then: remainingChildren = {{childArray.remove(childComma)}} Success! ISSUETMP-6809, ISSUETMP-6810, ISSUETMP-6811, ISSUETMP-7298, ISSUETMP-7302 YEESH. I recall you writing something (and filing a bug?) about how Automation is pretty flexible/lazy about…

Heya @Bill Sheboy I was trying to figure out how to do #3 without Automation having a shift() function. From the "Detect new Epic Created" rule, I'm sending this to the webhook: { "parentKey": "{{newIssueKey}}", "childArray": {{lookupIssues.key.asJsonStringArray}} } And in the "Create Child Function" rule I'm doing:…

Woof. I think there's a couple of issues with that. It's Bulk Create, not Bulk Clone. Reading the (admittedly sparse) docs, I don't see a way to reference a "source" issue to copy. So I'd have to get pass it the full content of each child task I'm cloning? (I mean it's probably just Summary and Description, but what if I…

Thanks for responding to the Bat-Signal, @Bill Sheboy (truly mixing the movie/tv references), I knew you'd come through. #1) Alas, no, the number of linkedIssues is variable, depending on the type of certification #2) My reaction while reading this was that I said "Oh god" then made this face: (I was gonna use clip art,…

Thanks - good point on ranking after creation, although what they really want is to see those child tasks in order while viewing the epic. Hum, will need to look at @Bill Sheboy 's suggestions.

OMG @Dirk Ronsmans they *still* haven't dealt with Unique Team Naming yet? I thought they would've resolved that when they the option to sync with Groups working. (I refuse to do any work with Teams until they fix that. Also, what even could you even do with Teams in Jira or Confluence with regards to JQL, CQL, Workflows,…

Hey @Elle Ky I know we're all busy as hell but since you are making active progress on moving from Will Support to Supported some of the items you originally posted, you should know that the forums make it really hard to see those changes. I think if somebody is watching this specific post they might see the change, but…

OMG, and thanks to a tip from @Susan Hauth _Toronto ACE Leader_ as well as a careful reading of the history of Legacy Editor Deprecation: High-Level Feature Support Overview (Championship has its privileges), I found that Atlassian introduced ANOTHER NEW FEATURE without any fanfare, much less documentation, much less…

That's wild @__ Jimi Wikman because I checked yesterday and I swear that when I searched for the word 'density' nothing came up, but lo and behold it's there now: Our Sandbox is on Preview, so I'm wondering what track (if any) you are on: (And can you really call it a "schedule" if it shows up the day AFTER it rolled out?)

OH DANG! @__ Jimi Wikman found it on January 20!? * Introducing compact density for pages and live docs Jimi wrote: Changed Rollout Schedule to Jan 20, 2026 Changed Status to Rollout Complete Where did you find that Jimi??

Thanks @Barbara Szczesniak yes, I totally missed including that very important screenshot. Here's a close-up view, with the hover-over tooltip: And yes @River Brandon, I too hate that hidden controls that only show up when you hover in the right place. I truly do not understand Atlassian's obsession with white space even…

I will note taking a closer look at my screenshots, that while the font size has gotten smaller, similar changes to margins and spacing between elements (paragraphs, panels, column dividers) are still EXACTLY the same, which makes me think they didn't have time to properly proportionally resize ALL the elements. I guess…

Ah, that's right, didn't realize Conditions inside of Triggers were new. And yes, I did have a small worry about a potential delay between issue creation and Request Type setting. So it sounds good to play it safe with a Re-fetch and a separate Condition block. And yes, fine point on the verbiage. Let's try: To ensure that…