Restrict subtask issueType options based on it's parent issue issueType

[Rodrigo Silva]

Hi everyone,

I'm trying to restrict available issue types on subtask creation, based on the issue type of it's parent issue. So, for example, for the issue type "Sample", on subtask creation, I want to have only one option "Issue subtask".
So far I've implemented the following script, as an initialiser function on behaviour, and then set it to issueType field:

import static com.atlassian.jira.issue.IssueFieldConstants.ISSUE_TYPE
import com.atlassian.jira.issue.Issue
import com.atlassian.jira.component.ComponentAccessor

Issue parentIssue = underlyingIssue.parentObject

def constantsManager = ComponentAccessor.getConstantsManager()
def sampleIssueType = constantsManager.getAllIssueTypeObjects().find { it.name == "Sample" }

if(parentIssue.getIssueType().equals(sampleIssueType)){
    def issueSampleIssueType = constantsManager.getAllIssueTypeObjects().find { it.name == "Issue subtask" }

    // In other cases, I'll need multiple options

    getFieldById(ISSUE_TYPE).with {
        setFormValue(issueSampleIssueType.id)
        setReadOnly(true)
    }
}

However, it is not working as expected (all issue types are available when I create a subtask of "Sample")

Can someone please help me on that?

Thanks in advance,

[Adolfo Casari]

@Rodrigo SilvaHi, were you able to resolve this somehow?

[Rodrigo Silva]

Hi @adam_gadomski , this issue was marked as fixed by Adaptavist.
However, I didn't have time to test it yet. You can try something, using this documentation : https://scriptrunner.adaptavist.com/5.4.47/jira/recipes/behaviours/restricting-issue-types.html#_restricting_available_issue_types

And this is the issue https://productsupport.adaptavist.com/browse/SRJIRA-1010

I'll appreciate your feedback, after the test  =)

Good luck,

[Aidan Derossett _Adaptavist_]

As it turns out, question is well warented and today I learned that this is actually a known bug in our current ScriptRunner back-log. You can go here -> SRJIRA-1010 - to see more details on the bug, I'm sorry I wasn't able to catch this before putting you through the additional trauma of creating a question on the Atlassian Community.

[Gonchik Tsymzhitov]

Hi! 

@Aidan Derossett _Adaptavist_ Do you know any plans to fix it? 

Cheers,

Gonchik Tsymzhitov

[JohnsonHoward]

Hi Rodrigo,

Your code should work if you remove the .parentObject from the underlyingIssue.

Just use underlyingIssue.

Let me know if that works.

Regards,

Johnson Howard

[Rodrigo Silva]

Hi Johnson, thanks for your help.

I've removed the, .parentObject, but it stills not working ...

Is there any full reference available, listing all available variables on that context (field initialization) such as "underlyingIssue"? I Know that there are some examples online using that variable, but a full reference would be great.

Also, "formField.setFieldOptions(Iterable)" seems to not work with collections (which is exactly the example showed on edit screen), how can I use this function (I'll need to allow multiple values for subtask issue type, based on parent's issue type)?

Thanks,