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; } } }

Date validator (30 days) - JMWE

RIZKY JTUASIKAL

Example:

Today is 05/25/2023 and if I create a task on 06/26/2023 (30 days) it will show an error message,

and if I create a task between the interval on 05/25/2023-06/25/2023 there is no error and the task is being created.

What is the query to get that result??

and what type of validator can I use??

Accepted answers

David Fischer

Hi @RIZKY JTUASIKAL ,

what do you mean by "I create a task on 06/26/2023"? Where is that date input? In a custom field?

All comments

David Fischer

Hi @RIZKY JTUASIKAL ,

what do you mean by "I create a task on 06/26/2023"? Where is that date input? In a custom field?

RIZKY JTUASIKAL

Hi @David Fischer ,

it doesn't use custom field/date input.

is that possible?

or does it have to use date input?

please advice,

thank you David

RIZKY JTUASIKAL

Example:

I created subtask A, and will record the creation date.

Created on 05/25/2023.

Then there is a rule if it is still within 30 days (bases on the date of subtask A creation),

I can still create another subtask,

(ex: subtask

but, if it exceeds 30 days, I can't create subtask B

David Fischer

So to summarize:

you create a main issue
you create a first sub-task on that issue
when you attempt to create a second sub-task on that issue, you want to disable the creation if the first sub-task was created more than 30 days earlier
when you attempt to create additional sub-tasks, you want to disable the creation if the oldest sub-task was created more than 30 days earlier

Is that correct?

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-software

jira-software-cloud

addon-com.innovalog.jmwe.jira-misc-workflow-extensions