Darryl Lee Community Champion

Oh yeah, I just did a bunch of sleep commands. :-} This isn't for anything in production where I'd need confirmation the rule ran successfully, but yes, that would definitely complicate things. My use case was: * Clone of a bunch of issues from a "template project" * Transition some of those issues to "Selected for…

Oh hey so tonight I was reading @Esther Strom's excellent article on Automating the creation of a Confluence page linked to a Jira ticket and noticed something about the Send Web Request action: It includes a validator! So Atlassian already has some code in Automations that is able to lookup an arbitrary Jira issue and use…

OH MAN, I love this idea. In fact, it gives me some ideas on how to automate (using shell scripts) manually running several automation rules that have to happen in sequence (where I could not figure out how to cleanly chain them together).

Ah, ok, there's already a feature request for this: * AUTO-64 - Improve Confluence integration - more Confluence actions in Automation for Jira And this would be really cool for integrating Smart Values from Jira into Confluence templates: * AUTO-86 - A4J Create Confluence Page - Add Affordance for Setting Values for…

Humph. It looks like Automation doesn't currently support the adding/replacing the actual body of a Confluence page. I found this add-on: * Elements Publish - create Confluence pages from Jira And this article that uses web requests from Jira to talk to the Confluence REST API directly for publishing page content: *…

Huh. So no way to edit/replace the body of a page in Confluence? I hope that's on the roadmap, because as it stands this is pretty limited if you wanted to programmatically generate pages in Confluence. You know, for a use case like this: Create confluence page based on issues set to specific status 

OOOOF, it looks like this only creates a page, but without content. I need to read up on the new Confluence automation feature to see if we can then figure out how to populate the content on the new page we just created. Originally I was going to do this with an incoming webhook trigger in Confluence that would be called…

Hey @James Wardle ! You can use a Scheduled Trigger to run every day at say, 11:59PM, and then I would use the Lookup Issues action to search for issues matching something like this JQL: project=YOURPROJECT and Status changed TO "Released to Production" ON {{now.convertToTimeZone("America/Los_Angeles").jiraDate}} (You…

Hi @Iga G - What's the name of your custom field? Is it the User Picker type? You should be able to simply select it in the Edit action from the "Choose fields to set..." drop-down (in my example below the field name is "Executor"), and then enter your smart value for the issue property, like so: 

Hi @Brandon Valley -- It looks like Analytics, including Page Views were added to Confluence Data Center (not Server) in version 7.11. (This was I assume a result of the acquisition of Good Software, who made a popular Analytics add-on for Confluence.) This is not available in Confluence Server. Furthermore, I do not see…

So glad you got it working! To understand a little more about Smart Values, specifically the one in question, {{lookupissues.size}}. When you use a Lookup issues action, it returns a list of issues. So you can then use list functions to get things like the number of issues it finds. That's what the .size part is about.

Can I build it with Jira Automation? I can access the API through that. :-}

Hey @Jan de Beijer OK, thanks for sharing more of your rule. I see the problem! The variables {{totalDevsubtasks}} and {{totalDevsubtasksDone}} must have the value of: {{lookupIssues.size}} This is the key. That is a Smart Value returned by the Lookup Issues component. They should look like this:

Hi Max - for permissions, Automation by default runs with the "Automation User" as the Actor. What is a rule actor? So then, if you want the rule to run as yourself, with your permissions, you should change the actor to you. Here's the details on that: Run Jira rules as another user Hope this helps, and I'd appreciate it…

Hi @Maeneth - I found this KB article that I think should answer your question: How to restrict customers access to specific projects only in Jira Service Management 

Hey yeah, hopefully we are getting closer! So the Log action doesn't actually do JQL queries or anything. It can basically only "print" stuff, like whatever variables you already have. SO to get the counts, you could just insert Log action after each Create variable component like this:

Who me, validate my rule? Haha. :-} OOOF, I realize now that I don't think my hack was actually working, or at least not fully. The other rule was still running. ODDLY though, for a while TWO tickets were getting created for each new project. Hmmm.

[Making this a separate answer] Now that I think I understand @Jamshaid 's requirements, to be able to put the same URL on every "Start Work" screen, I realize this would be better implemented as a Message Custom Field. Message Custom Fields can include HTML, like your URL. (so you will need include the <a href...</a>…

Hi @Matthew Kasper - this is a great idea, because yeah, that UI really sucks. I mean, what other project would a Sub-task even even be created in? That's dumb. (It's probably because they're using the same code for regular Issue creation, which could be in another project.) Anyways, I'm not sure why, but I was able to…

@Brock Jolet - YES. I pretty much always end up starting with Manual Trigger rules for this reason. I like your idea, but I think it'd be better if they just updated the existing "Validate query" functionality they already have for JQL fields. They've added things like "Insert account id" and "Resolve users". What they…

Thanks - yeah, configuration looks right to me. I have not seen that error before about "Could not find create meta data for project/typeId", but it looks like others have seen it: https://community.atlassian.com/t5/Jira-Software-questions/Simply-automation-error/qaq-p/1458621 I guess you might try @Bill Sheboy's…

Glad you found it! Would you mind please clicking the [Accept Answer] button up at the top of this page? Thanks!

Hi - I saw you were having some problems. Hm now that I know what your trying to do, maybe change the Scope back to All or maybe Projects of specified type (Software development)?

Hrm, I just tested again and it doesn't matter if the trigger specifies transition to Done or not (although you should probably do this to reduce the # of times the rule runs, as that can be limited, depending on your tier). I can see my issuetypes are different depending on which sub-tasks I transition. The question is…

Hi - I got this to work for me with issuetype. I made my rule look just like yours. So are you saying that CN-118 is NOT a Development sub-task? That's odd. The first IF statement should have not matched and you should be seeing "No actions performed", not "Success". OH! One difference I noticed is that your trigger is not…

AH, ok, thanks for the clarification. So the key is that ALL of the subtasks of a certain type (let's stick with a Custom Field I've named "Subtask Type") have to be done. Got it. I think this should work: The trick is that I'm doing two Lookups: parent={{issue.key}} AND "Subtask Type" = "Development" That's all of…

Oh hey @Max Twemlow I was testing some other Automations, and they triggered an error from my First Blood automation because my new test issues did not have associated Sprints. So you probably will want to add this right after the trigger: Issue fields condition: > Field: Sprint > Condition: is not empty

So I didn't like having to make @Potip Serhii manually choose every field to copy, so I started thinking about whether I could "clone" an issue by pulling the data from an API call to get all the field data in JSON format and then just plopping that into Additional fields in the Create action and lo and behold... it works…

Thanks for the screenshot! So is Author the same as Initiator? I assume so. So I think you won't be able to use the actual Clone Action because that always uses the "current issue" as the source of the clone. But what I think you *should* be able to do is Create a new issue in the new project with the looked up data. To…

Hi @Jan de Beijer - So I'm going to go forward with your example assuming they are not optional, but requirements. Note that this does not check to see if you have exactly 8 subtasks. It does check if you have exactly 3 subtasks with custom field X filled and exactly 5 subtasks where custom field is empty. You'll probably…