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

automatic subtask due date creation based on parent due date -14 days (Scriptrunner)

erin_4408zw

Basically I am trying to take the required parent due date, subtract 14 days from it and apply it to my subtask's due date field.

Currently it is setting the subtask due date as the created minus 14 days which is not what I want.

I want to set the parent to Apr/20/20 and then the subtask automatically, upon creation through a transition, sets its own due date to Apr/06/20.

The code I have right now in my subtask additional issue actions is:

import com.atlassian.jira.issue.Issue;
import com.atlassian.jira.issue.MutableIssue;
import java.sql.Timestamp;

MutableIssue myIssue = issue;
Calendar dueDate = Calendar.getInstance();
myIssue.setDueDate(new Timestamp((new Date() - 14).time));

Any help would be much appreciated

Accepted answers

All comments

fjodors

If I understand you correctly you need listener that fires when issue is updated
In listener you can
a) check if this is parent issue.
b) get parent issue due date
c) get all subtasks of this issue
d) update due date of each subtask.

Something like this:



Issue currentIssue = event.issue;

if(!(currentIssue.isSubTask())){
//this is parent issue
//get due date
Timestamp dueDateVal = currentIssue.getDueDate();

//then you can update due date of this issue
//review all subtasks and perform any operations with them

//e.g. update parent issue
MutableIssue issueToUpdate = (MutableIssue) event.issue
issueToUpdate.setDueDate(Timestamp '<your new dueDate value for parent issue>');

//get collection of subtasks
Collection<Issue> subTasksCol = currentIssue.getSubTaskObjects();

//iterate colleaction with subtasks and update duedate of each of them
for (Issue subTaskEl : subTasksCol) {
MutableIssue subTaskM = (MutableIssue) subTaskEl;
subTaskM.setDueDate(Timestamp '<your new dueDate value for subtasks>') 
}

}

erin_4408zw

The parent due date will not be changed since it is required upon creation. So parent due date won't need to be updated. Upon transition of the parent to In Progress, the subtasks are all generated and need to have the parent due date set. I would prefer to use a post function for this, but I can try the listener and see if it throws any errors or gives me any issues.

erin_4408zw

Tried to test and it won't run. I set up a custom listener to fire when the the "issue updated" event occurs. Did not run once. Maybe I'm misunderstanding where to place this?

Also the Timestamp code gives me an error so I tweaked it to follow my code posted above.

import com.atlassian.jira.issue.Issue;
import com.atlassian.jira.issue.MutableIssue;
import java.sql.Timestamp;

Issue currentIssue = event.issue;

if(!(currentIssue.isSubTask())){
//this is parent issue
//get due date
Timestamp dueDateVal = currentIssue.getDueDate();

//then you can update due date of this issue
//review all subtasks and perform any operations with them

//e.g. update parent issue
MutableIssue issueToUpdate = (MutableIssue) event.issue
issueToUpdate.setDueDate(new Timestamp((new Date() - 14).time));

//get collection of subtasks
Collection<Issue> subTasksCol = currentIssue.getSubTaskObjects();

//iterate colleaction with subtasks and update duedate of each of them
for (Issue subTaskEl : subTasksCol) {
MutableIssue subTaskM = (MutableIssue) subTaskEl;
subTaskM.setDueDate(new Timestamp((new Date() - 14).time));
}
}

fjodors

1. you need to put your custom listener here

Manage apps -> Script listeners

2. Try to enable logging

import org.apache.log4j.Logger
import org.apache.log4j.Level
import org.apache.log4j.Category

//for log levels
Category log = Category.getInstance("com.onresolve.jira.groovy")
log.setLevel(org.apache.log4j.Level.INFO)
log.info("start logging ");

Welcome!

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

Quick Links

Find more posts tagged with

server

scriptrunner

jira

adaptavist

jira-server