nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

I'm having trouble writing the automation for a task due date to be 1 week before an event date.

Lisa Mills

I'm setting up an automation for recurring events. Since our process is the same for each event and tasks are typically due at the same timeframe based around the event date, I'm trying to write the smart value to automatically set a due date for a week before an event date. Can someone please help me with this value. I'm afraid I don't understand it with the articles in here. I kind of need this one broken down like I'm 5 years old, please...

Accepted answers

Trudy P Claspill

Hello @Lisa Mills

Please provide screen images that show the complete rule you have constructed so far.

What is the name of the field where you record the "event date"? What type of field is it; just Date or Date/Time?

When is the event date filled in?

What if the event date is changed?

All comments

Trudy P Claspill

Hello @Lisa Mills

Please provide screen images that show the complete rule you have constructed so far.

What is the name of the field where you record the "event date"? What type of field is it; just Date or Date/Time?

When is the event date filled in?

What if the event date is changed?

Kalyan Sattaluri_iinm1n

Hello @Lisa Mills

When you say, automation for recurring events, what do you have in mind? Send daily emails? Set up tasks? Share some of your thoughts on what do you want to do given that time window is here.

Also, this event date you mentioned, is this value stored some where? Maybe in a field in a story etc.. Or is it a pattern like 1 day of every month, or bi weekly etc?

I am hoping you are not completely new to automation as we can share the recipes based on what you mention, but its always good to be familiar with what it can do so you can adjust these as you need when time comes.

Please share your feedback.

Lisa Mills

Here is the build I'm working on. The two dates inside the red box are what I'm trying to manipulate. I want to be able to set the event date when I create the parent task. The child tasks are the automation and I'd like to be able to set certain task to have due dates based on when that date is set to. For example, this rule shown would be one week before the event date. By the time it's getting put in here, the date is set and does not change. It's a webinar, so there's no reason to change it. I hope this addresses your questions... Screenshot 2024-02-20 161202.png

Lisa Mills

I'd be happy to explain. We do a webinar with a business partner monthly. There are tasks that need to be completed for each occurrence of this webinar. I'm trying to set up an automation, so that when I say it's this type of event, it populates those tasks and due dates based on the event date I set upon creation. I'm attaching the screen grab here. The red box are the dates I'm referring to. Thank you for your help! Screenshot 2024-02-20 161202.png

Trudy P Claspill

So your rule is triggered when a "ChiroTouch Webinars" type of issue is created.

Then your rule tries to create a new issue of type "To Do" in the project "Marketing". And you want to set the Event Date and Due Date in that new issue.

Question 1: In what project does the ChiroTouch Webinars issue get created?

Question 2: You said the Due Date should be a week before the Event Date. But what should the Event Date in the "To Do" issue be getting set to?

I also see that you are trying to make the ChiroTouch Webinars issue the parent of the "To Do" type issue. Can you explain your issue hierarchy?

By default Jira's issue hierarchy has three levels:

Epic (a built in issue type)
|-- "standard" level issues (i.e. Story, Task, Bug)
    |-- "subtask" level issues

You can create new issue types at the "standard" level, and you can create new issue types at the "subtask" level (but only for Company Managed projects).

An issue can have as its parent only any issue for the level directly above it.

So I am curious about you two new issue types and in which level each exists. You may not be able to make the Chiro issue a parent of the To Do issue.

Also, are what is the Type of the project(s) where you are creating these issues? You can get that information by going to the Projects menu, selecting View all projects, finding your project on the list, and looking at the Type column.

Lisa Mills

Basically, this is our Marketing Board. It's broken down by months. From there, each event or marketing campaign is its own issue. From there, each issue has its individual tasks that need to be completed for that campaign. I'm attaching the screenshot of how I use Jira. This one is specifically for a recurring event we call a ChiroTouch Webinar. We have 4 activities, the one in the first screenshot is the first activity. The event date is set on the ChiroTouch startup and there is a rule for that to carry through to any child issue. That was an automation I had set up a long time ago, so I just assume it can run that rule then, the due date rule. Screenshot 2024-02-20 163846.png

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud