Darryl Lee Community Champion

OMG @Kathy Hart YES Schlotzky's. I discovered it the summer I spent working in San Antonio. I must've eaten there a few times a week as well. @Esther Strom pretty sure "what it was" was all the grease in the bread. God I love that bread. :-} So then, although it didn't always agree with my stomach later in the day, I…

Hey, so I finally did some testing (imagine that!) and can confirm that the hack to *60 all of the estimates did work. But I came here to specify that this only works in the CSV Importer that is available when you are in Advanced issue search: There is another way to import CSVs, via the External System Import and if you…

Hi @habib rahman - can you please provide links to the add-ons you listed in your answer? I cannot find any that match those names. Also, do you have direct experience with any of those add-ons? @INACTIVE 20250730 - April Glover maybe a better option would be to explore the Atlassian Marketplace yourself and look at the…

Hi @akash.ramtohul -- Apparently there is a known bug with importing Original Estimate, where the values are divided by 60. In this question and answer thread I'm seeing people say that they put in 3600 "seconds" and it shows up as 1 minute instead of 1 hour. Similarly, somebody else reported putting 72000 seconds and it…

Good point @Joe Pitt Yeah, @Charlie Banks if you want to make sure the Label has *changed* before moving to the next step, you'll also need a "Field(s) Changed Validator", like from Scriptrunner. JMWE also provides a "Field has been modified validator", and I suspect JSU also has one. Also, I should have linked to this…

Hi @Shelli Kleman - I think your values for fixVersions need to be enclosed in double quotes, like: "1_0_1 - Day 1 Patch" ALSO - when I've tried to do advanced editing with JSON in the past, despite it making it impossible to read, I've had to sometimes remove the linefeeds, so your name value would end up looking like…

Hi @Andreas Springer _Seibert Group_ - So it might be nice to have something like Announcement Banners back in Cloud, so that we could tell people if there's going to be an outage for maintenance or something. Oh wait, with Cloud there's never any (ahem) scheduled outages. Well, it would also be good for…

On Jira Server you'll need a plugin that provides a "Field Required Validator", which you would apply to the transition used for closing the ticket. Here's an answer from @Rachel Wright on how to do this with ScriptRunner: * How to make a field required during a workflow transition? Other add-ons that provide a similar…

Aw man. We really need to be able to SORT both lists and then DIFF them. Hum.

Due to some intense windstorms on Tuesday, many of us in the SF Bay Area were without power for at least 24 hours, and some friends STILL do not have power coming up on 48 hours, and for some of them the estimate from our utility provider PG&E (yes, the one you may have heard about) is that their service may not be…

Hi @Eoin Curran, are you intending to upload all the videos on your Confluence server? I don't think that will work, as I'm not aware of a way for Confluence to play different videos based on clicking certain links. That sounds like it would involve some fancy JavaScript programming, which Confluence doesn't really allow.…

@Bruno Altenhofen wrote a whole article on how to do exactly what you're trying. * Populate a user picker field from the description field Sorry about the earlier journey to get to the exact same place.

Ugh, I spoke too soon. There is a way with the Find Users API: https://YOURSITE/rest/api/3/user/search?query=fb-test@darryl.com So then, this rule got a lot more complicated, because you'll need to use a Web request action to the Jira API to try looking up the email address to see if it has a corresponding accountId, and…

Ugh. Further complications. I think Request Participants cannot be added by email! When trying to add an active user by email address, I'm seeing this in my logs: Inactive user fb-test@darryl.com So uh, that's not great. Oooof, of course the estimable @Bill Sheboy has already run into this issue. * Automation to Add…

Oh, because I have a tried lot of add-ons that generated service accounts, I did want to show how you might need to scroll through list of accounts before you can see the Smart Value at the bottom of the list when trying to use it for Request participants. 

Hi @Mehran Ahmadi - So I think this should work, using the match operator for smart values: {{issue.description.match(".*E-Mail Adresse =(.+).*")}} Ah, one catch is that I entered an email address via the GUI, which converted it into a link. So my code above extracts the address as Jira markup for the "link":…

Does this transition require you to add a link to BRP? If so, then the rule will work fine. Or are you wanting to add this comment only during this transition, if the link to BRP was added outside of the transition? And is the transition for BRP tickets or other projects? Assuming this is a transition for the DMM project…

Hi @Sami Ahmed Shaik - so you only want to add this comment for BRP project links? If so, then I would do something like: Trigger When: Issue linked Condition Advanced compare condition: {{destinationIssue.project}} equals BRP Action Add comment

Ok, if you're somehow going to be able to train/limit your users to only add ONE Request Participant at a time, then you could do this with a Web Request to Jira's Rest API. You can make a call to this endpoint to "lookup" the email address: https://YOURSITE/rest/api/2/user?key={{fieldChange.to.replace(fieldChange.from,…

Ooof. Yeah, I don't like having to use a custom field for this. I wonder if you could instead set an issue entity property for "lastAddedParticipant", as mentioned here. You'd probably have to then do a Re-fetch Issue data before that property is then available as {{issue.properties.lastAddedParticipant}}. I'll see if I…

OH. I just realized what the problem might be. We're trying to use {{fieldChange}} within a {{#issue.customfield_10000}} So what it's looking for is: {{issue.customfield_10000.fieldChange.to}} Which um, yeah, is not valid. We need to way to reference the "global variable" {{fieldChange}} inside of the iteration of the…

Oh man @Trang Ngoc Nguyen this is a clever idea! (Check it out, @Bill Sheboy :-) But I also could not get it to work on Jira Server 8.20.10. I even added this check for a specific user (via the audit log) , and it came back positive: Match? {{#if(equals("JIRAUSER10105", fieldChange.to.replace(fieldChange.from,…

Hi @[deleted] - One option is to export all your project metadata from your instance as JSON using the REST API: https://YOURSITE.atlassian.net/rest/api/3/project If you are not familiar with using tools like jq or python to work with JSON, I found this good guide for importing JSON into Excel: * How to Convert a JSON File…

@Nichols Wood Balloon Delivery? I'd love to hear how you use Atlassian products in your business!

Hi @Marcus Jones - another option is to simply count the number of attachments, using the smart value: {{attachment.size}} The trick is that the "Issue Created" trigger will probably fire before all of the attachments are attached. Yup - the first time I did this I got 0. So I pulled the old "Re-fetch issue data" trick and…

Glad it worked @Webert! Thanks for catching my missing closing </a> tag! 

Hi @Webert - your JQL is just fine. The trick is where you use it. If you use the Lookup issues action block you can create an email for each distinct project, including a the project's name, key, and link. Here's what I came up with: The {{lookupIssues}} smart value includes all issues found in the JQL query. But if you…

Hey there, so yeah, what I forgot is that the match function will only create "lists" if there are multiple matches. In the case of only 1 item, it just returns a single string. So then, we need to check if that's the case (using the isNumeric function), and if so, just create the one item. (Note that change to the smart…

Now that I've seen this implemented "for real", I realize that I was wrong about having to duplicate components. Instead, you could simply use Summary to store Component Name, and your Assign action would use: {{lookupIssues.first.summary}} This avoids the whole problem of having to duplicate Components to your *LOOKUP…

You might also want to change your email body so that the HTML is actually correct: {{#lookupIssues}} * <a href="{{url}}">{{key}}</a>: {{summary}}:{{issuetype.name}} {{/}}