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

Based on parent ticket transitioning status, show or hide options in subtask tickets

VVC

We have a unique requirement to display or hide options under a drop down custom field in all subtasks on both create or edit screens based on the parent issue type ticket status. Any leads on how to achieve this solution would be greatly helpful for us using Adaptavist behaviors or other possible alternate solutions?

For example:

This should cover two scenarios.

#1 - When a parent change ticket status is in any status other than APPROVED, then the custom drop down "Deployment Environment" field in the change subtask ticket should display only "DEV", "UAT" for selection on both CREATE and EDIT screens.

#2 - When a parent change ticket status is set to APPROVED, then the custom drop down "Deployment Environment" field in the change subtask ticket should display "DEV", "UAT" and "PROD" for selection on both CREATE and EDIT screens.

Accepted answers

Stefan Stadler

Hi VVC,

you are basically asking for two different questions:

1. How can I get the status of the parent issue?

2. How can I hide an option in a dropdown list?

The answer to your second question seems to be covered here already: Solved: hide options from select list field values based ... (atlassian.com)

Regarding your first question, this seems to be fairly simple:

issue.getParentObject().status.name

You may combine this like that in an initializer for your subtask issue:

if(issue.getParentObject().status.name == "APPROVED"){
    //show the prod option
}
else{
    //hide the prod option
}

Hope this helps

Regards, Stefan

All comments

Stefan Stadler

Hi VVC,

you are basically asking for two different questions:

1. How can I get the status of the parent issue?

2. How can I hide an option in a dropdown list?

The answer to your second question seems to be covered here already: Solved: hide options from select list field values based ... (atlassian.com)

Regarding your first question, this seems to be fairly simple:

issue.getParentObject().status.name

You may combine this like that in an initializer for your subtask issue:

if(issue.getParentObject().status.name == "APPROVED"){
    //show the prod option
}
else{
    //hide the prod option
}

Hope this helps

Regards, Stefan

VVC

Thanks @Stefan Stadler for this reference. I will give this a try and see how it works for me.

VVC

I found another source reference, where this below script that was added under behaviors - Initialiser seems working only for EDIT but not for CREATE subtask action.

Any suggestions on how to get this working on the creation of subtask as well?

import com.atlassian.jira.component.ComponentAccessor

def issue = underlyingIssue

def customFieldManager = ComponentAccessor.getCustomFieldManager()

def customFieldId = "customfield_xxxx" // The custom field in the subtask

def customField = customFieldManager.getCustomFieldObject(customFieldId)

def formField = getFieldById(customFieldId)

if (issue.isSubTask()) {

    def parentIssue = issue.getParentObject()

    if (parentIssue.getStatus().getName().equals("Approved")) {

        // Show options

        formField.setFieldOptions(["QA", "UAT", "PROD"])

    } else {

        // Hide options

        formField.setFieldOptions(["QA", "UAT"])

            }

        }

Stefan Stadler

Hi VVC,

I am pretty sure that behaviours also work in sub task create actions. In fact, I have just tried out a simple example:

getFieldByName('Business criticality').setFieldOptions(['normal'])

There is another value existing usually, but this was not available after this.

Additionally, it is needed to use the issueContext as the issue you are about to create does not actually exist in the create screen. That is why underlyingIssue is not initialized.

And therefore, getting the parent has to be done by the "field" parentIssueId.

So based on what I tested quickly, this should be your solution:

import com.atlassian.jira.component.ComponentAccessor

import com.atlassian.jira.issue.IssueManager

import com.atlassian.jira.issue.Issue

//only run if the issue to be created is a Sub-task

if(getIssueContext().getIssueType().name=="Sub-task"){

    //get parent issue

    def parent = getFieldById("parentIssueId")

    Long parentIssueId = parent.getFormValue() as Long

    IssueManager issueManager = ComponentAccessor.getIssueManager()

    Issue parentIssue = issueManager.getIssueObject(parentIssueId)
    
    //this sets the parent issue from the underlyingIssue if it is not set
    //this handles Edit screens

    if(!parentIssue){

       parentIssue = underlingIssue?.getParentObject()

    }

    //get field to change

    def field = getFieldByName('your field name here')

    //change values based on status name

    if(parentIssue.status.name == "Approved"){

        field.setFieldOptions(["QA", "UAT", "PROD"])

    }

    else{

        field.setFieldOptions(["QA", "UAT"])

    }

}

Let me know, if this helped solving the issue

Stefan

Welcome!

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

Quick Links

Find more posts tagged with

server

jira

jira-server

jira-data-center

data-center