hi all, is there any way to force JIRA not to accept sub-task due dates that go beyond the parent's issue due date? Eg: * parent issue due date is set to Feb 15, 2012 * sub task due date should not be allowed to be set beyond this date. Any date before Feb 15 should be accepted. From my reasoning this should be a condition during the issue creation process... Any suggestions? thanks, Jacques.

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

Limit sub-task due date not to pass parent issue due date

Jacques

hi all,

is there any way to force JIRA not to accept sub-task due dates that go beyond the parent's issue due date?

Eg:

parent issue due date is set to Feb 15, 2012
sub task due date should not be allowed to be set beyond this date. Any date before Feb 15 should be accepted.

From my reasoning this should be a condition during the issue creation process...

Any suggestions?

thanks,
Jacques.

Accepted answers

Nic Brough -Adaptavist-

You'll need to find or write a "validator" to do this (a "condition" will stop a transition from being offered to a user - that's a bit too early in the lifecycle)

All comments

Nic Brough -Adaptavist-

You'll need to find or write a "validator" to do this (a "condition" will stop a transition from being offered to a user - that's a bit too early in the lifecycle)

Jacques

thanks Nic,

where would I look for such a validator? I (still have no) experience with programming in/for JIRA.

thx,
Jacques.

Renjith Pillai

Was wondering, it should be rather the other way, the parent task due date should get shifted as per the latest due date from the sub-tasks. Isn't it?

Nic Brough -Adaptavist-

https://plugins.atlassian.com/ is the place to start.

Nic Brough -Adaptavist-

It absolutley depends on your process.

But I'd say that in the majority of cases, no - you would not want a parent issue to have it's due date amended by a sub-task - if that happens, your main task would have been changed, probably without any oversight by a human. Jacques approach feels more correct - if a human needs to push a sub-task out past the main task's due-date, then it's very likely that a batch of humans need to know, and discuss the problem. As someone who has to deliver stuff to deadlines, I absolutely would NOT want my deadlines being changed just because we're breaking up work into bits.

Jacques

Thanks Nic! On my way there now!

Welcome!

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

Quick Links

Find more posts tagged with

jira

due-date

sub-task