Dear ALL,
is there a way to implement in the Jira Data Center (I use version 9.12.5) the powerful Jira Cloud feature of the lookupIssues on the due date field?
Thanks in advance,
Vincenzo.
Hello @vincenzo.spatafora
What do you mean implement lookupIssues on Due Date field, as in access Due date field in the response of lookupIssues JQL?
Thank You @Kalyan Sattaluri for your reply.
Yes, correct and my JQL in the Lookup issues is "issue in childIssuesOf("{{issue.key}}")".
And afterwards, in log action, my log message is "List of Sub-Tasks is {{lookupIssues.key}} and the Due Date is {{lookupIssues.duedate}}".
From the Audit log, the list of the sub-tasks is nicely reported but NOT the due date.
Do you see a reason for that?
Unfortunately, in Data Center, lookupIssues exposes only certain (basic) fields and we dont have option to expand that list.
It needs to be an update from Jira itself where they are expanding available fields like it is in Cloud, where all fields are accessible.
But, looking at your post, if all you want is to access sub-task fields, you dont need to do lookupIssues.
You should be able to reference it as {{issue.subtasks.key}} & {{issue.subtasks.Due date}}
Please try and let me know if issues..
Thanks @Kalyan Sattaluri , appreciated your help.
I was trying that: the trigger of my rule is an issue transition: how can I pick all the associated sub-tasks?
And also, I need to take the max due date of all the sub-tasks tickets.
What would be the syntax in this case?
Kind Regards, Vincenzo.
It looks like you're new here. Sign in or register to get started.
