Brock Jolet Rising Star

I have a project with a pretty complex workflow. The project admin would like to use subtasks to track the many steps for a given task. This results in upwards of 30 subtasks per task. My goal is to provide a manual trigger for the user that will generate the standard subtasks on the particular issue that is selected. I've…

I understand that being on the cloud platform means we will get updates to the UI from time to time, but sometimes those changes are inconvenient. Today I noticed an update to the Automation results that introduced pagination. This in itself is fine, but there should be an option to display ALL rules and more importantly…

Oftentimes Automation rules get implemented to fix a problem but are only re-visited when something breaks or requirements change. When it is time to refactor a rule, context is very important. Even if the person revising the rule is the same as the person that created it, it may be difficult to remember all of the details…

Using Jira Automation, I am able to trigger a rule based on a project being created. I want to use this to send a heads-up email to the admins. I'm having trouble figuring out the smart value for capturing the project name. Normally, I would grab the value from a specific issue using {{issue.project}}, but since a new…

I'm editing an automation that has existed for a while by adding an additional else statement. I was able to do so, but within that else statement I can no longer directly add an in-line conditional. The existing else statement already had an in-line conditional and I was able to drag it to my new one, but when I try to…

I've got a very simple query that I'm using in a Lookup step of an automation that returns Epic issues with a specific label. project = Finance AND type = Epic AND labels = month ORDER BY created DESC I would like to reference only the most recent Epic, which should be the first result. I can't figure out how to do an…

I have a convoluted setup where one automation triggers a webhook that in turn triggers a second automation. On the second automation I am thus unable to use {{initiator.displayName}} to display who originally caused the chain of events. What I was able to do is capture the initiator in the first automation and pass it…

I am trying to create an automation and am running into a roadblock that regularly pops up. I need to be able to address issues that are two steps away from the trigger issue. Example: I have an automation that runs on a schedule and clones all issues with a specific combination of fields. I'm essentially using this to…

I am trying to create an automation that will clone an issue and update the due date to a specific date depending on input from two custom fields. For example, the user may choose to clone the task monthly on the 3rd of the month. They may also choose to clone the task annually on the 15th of the month. I have one custom…