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

Hide Custom Field on Parent Issue Based on Child Issue Status in JIRA Data Center

Digvijay Singh Gehlot_fgm3gu

Hi Community,

I want to hide a custom field present on Parent issue when the Parent issue is in Done status and all its Child issues (linked by Parent Link field) are in Done status as well.

Here, Parent issuetype = Initiative and Child issuetype = Portfolio Epic and I am using Parent-Child linking via Parent Link field.

How can we achieve this using scriptrunner behavior? Any sample code for reference would be a great help.

Thanks

Accepted answers

All comments

Salih Tuç_ktm7z2

Hi @Digvijay Singh Gehlot ,

If there is a parent-child relationship; then it is quite easy to solve that problem.

You need to:

Create a behavior for the Parent issue
Inside the script in this behavior, access to its subtasks
Filter the subtasks and check the statuses.
Depend on the decision hide/show the field

Thus:

def theField = getFieldById("customfield_xxx")

if(underlyingIssue.status.name == "Done"){
  def filteredSubtasks = underlyingIssue.subtasks.findAll { it -> it.issuetype.name == "Portfolio Epic" && it.status.name != "Done" }

  if(filteredSubtasks.size() > 0){
    theField.hidden = true
    theField.formValue = null
  }
  else[
    theField.hidden = false
    theField.required = true
  }
}

As an alternative, you may check by searching over JQL but I think the above code will work for you. Just don't forget to change the customfield's id.

Digvijay Singh Gehlot_fgm3gu

Hi @Salih Tuç

Thank you for your message.

I tried to run your suggested code but unable to see the changes on the UI.

I refined the code as per my requirement as below:

def radioTypeField = getFieldById("customfield_XXXXX")
def parentIssueTypeName = underlyingIssue.issueType.name
def parentStatusName = underlyingIssue.status.name

// Using Advanced Roadmap hierarchy such as Portfolio Parent as Initiative and Portfolio Child as Portfolio Epic
if(parentIssueTypeName == "Initiative" && parentStatusName == "Repository"){

// All Portfolio Epic Children are linked with Initiative via Parent Link custom field instead of Subtasks 
def childIssues = underlyingIssue.getSubTaskObjects().findAll 
{ 
it -> it.issueType.name == "Portfolio Epic"
   && it.status.name == "Done" }

// Portfolio Epic Children can be one or more and are in Done status already 
if(childIssues.size() > 0)
{

// Radio Type customfield should be editable and required
radioTypeField.readOnly = false
radioTypeField.required = true
}
else {

// Radio Type custom field should be in ReadOnly, Not required and set to None
radioTypeField.readOnly = true
radioTypeField.required = false
radioTypeField.formValue = null
}
}

I observed that, the code is showing Green but Radio Type custom field is still showing in ReadOnly mode on Parent issue although Parent is in Repository status and a Child (linked to Parent via Parent Link) is in Done status.

So, I have following questions below:

1) Parent issue is created in Parent project and Child issue is created in Child project. Will getSubTaskObjects() work with Parent Link field as used in above code?

2) Do I need to map both Parent and Child projects and their issue types in single behavior to fulfil the requirement?

Could you help me further with the above and it would be great if you can also share how JQL query is used within behavior script as an alternative to achieve my usecase.

For example: I have created a query which shows all those Parents where their Children are in Done status (and Parent Link is not empty)

Children Filter: project = CHILD AND status = "Done" AND "Parent Link" IS NOT Empty

JQL query:

project = PARENT AND issueFunction in portfolioParentsOf("filter = 'Children Filter'") AND status = "Repository"

I am looking forward to hearing from you soon.

Thanks

Salih Tuç_ktm7z2

The "Parent Link" is exactly states for Task/Story->Sub-task relationship; so yes it would work.

Remember that you should change the customfield_XXX with your field id (e.g customfield_12345). And also, you should place the script in initializer.

I think we forgot the outer else for the condition. Here is an updated code:

def radioTypeField = getFieldById("customfield_XXXXX")
def parentIssueTypeName = underlyingIssue.issueType.name
def parentStatusName = underlyingIssue.status.name

// Using Advanced Roadmap hierarchy such as Portfolio Parent as Initiative and Portfolio Child as Portfolio Epic
if(parentIssueTypeName == "Initiative" && parentStatusName == "Repository"){

// All Portfolio Epic Children are linked with Initiative via Parent Link custom field instead of Subtasks 
def childIssues = underlyingIssue.getSubTaskObjects().findAll 
{ 
it -> it.issueType.name == "Portfolio Epic"
   && it.status.name != "Done" }

// Portfolio Epic Children can be one or more and are in Done status already 
if(childIssues.size() > 0)
{

// Radio Type customfield should be editable and required
radioTypeField.readOnly = false
radioTypeField.required = true
}
else {

// Radio Type custom field should be in ReadOnly, Not required and set to None
radioTypeField.readOnly = true
radioTypeField.required = false
radioTypeField.formValue = null
}
} 
else {
  radioTypeField.readOnly = false
}

And also, you wrote this part wrongly: it.status.name != "Done"

This should be "not equal" since if the count of not "Done" issues is important for us. Please review the first code that I shared and this one.

Digvijay Singh Gehlot_fgm3gu

Hi @Salih Tuç

I followed the same as you guided with the below code in Initialiser and I also added log debug to see where it is landing in the if-else:

import org.apache.lo4j.Logger
import org.apache.log4j.Level

def radioTypeField = getFieldById("customfield_17500")
def parentIssueTypeName = underlyingIssue.issueType.name
def parentStatusName = underlyingIssue.status.name

def log = Logger.getLogger(getClass())
log.setLevel(Level.DEBUG)

// Using Advanced Roadmap hierarchy such as Portfolio Parent as Initiative and Portfolio Child as Portfolio Epic
if(parentIssueTypeName == "Initiative" && parentStatusName == "Repository"){

// All Portfolio Epic Children are linked with Initiative via Parent Link custom field instead of Subtasks 
def childIssues = underlyingIssue.getSubTaskObjects().findAll 
{ 
it -> it.issueType.name == "Portfolio Epic"
   && it.status.name != "Done" }

// Portfolio Epic Children can be one or more and are in Done status already 
if(childIssues.size() > 0)
{
log.debug("Entered in Parent-Repository & If C>0")
// Radio Type customfield should be editable and required
radioTypeField.readOnly = false
radioTypeField.required = true
}
else {
log.debug("Entered in Parent-Repository & Else")
// Radio Type custom field should be in ReadOnly, Not required and set to None
radioTypeField.readOnly = true
radioTypeField.required = false
radioTypeField.formValue = null
}
log.debug("Entered in Parent-Repository But Outside of If & Else")
} 
else {
log.debug("Entered in Parent-Not Repository")
  radioTypeField.readOnly = false
}

But it seems, Radio Type Field is still in ReadOnly mode although Parent is in Repository and Child is in Done statuses.

And the log says:
Entered in Parent-Repository & Else

Entered in Parent-Repository But Outside of If & Else

but it is not entering "If childIssues > 0" condition, when Parent is in Repository & Child is in Done i.e. Entered in Parent-Repository & If C>0

I want to see Radio Type Field as Editable and Required when Parent is in Repository and Child is in Done, apart from this Radio Type Field should be in ReadOnly.

Please guide if I am still missing anything in the code, I am new to groovy coding.

Thanks

Welcome!

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

Quick Links

Find more posts tagged with

scriptrunner

custom-field

jira

adaptavist

addon-com.onresolve.jira.groovy.groovyrunner

jira-server

groovy

jira-data-center

behaviours

status

data-center

jira-misc-workflow-extensions

appfire

parent

child

parent-link

app-central