Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,458,249
Community Members
 
Community Events
176
Community Groups

Scriptrunner behaviour not working with getFieldById(getFieldChanged()) mapped to issuetype field

import com.atlassian.jira.ComponentAccessor
import com.atlassian.jira.component.ComponentAccessor
import com.atlassian.jira.ComponentManager
import com.atlassian.jira.issue.CustomFieldManager
import com.atlassian.jira.issue.Issue
import com.atlassian.jira.issue.MutableIssue
import com.atlassian.jira.issue.comments.CommentManager
import com.atlassian.jira.issue.fields.CustomField
import com.atlassian.jira.util.ImportUtils
import com.atlassian.jira.user.util.DefaultUserManager
import com.atlassian.crowd.embedded.api.User
import com.atlassian.jira.issue.IssueManager
import com.atlassian.jira.user.util.UserManager
import static groovyx.net.http.ContentType.*
import static groovyx.net.http.Method.*
import static com.atlassian.jira.issue.IssueFieldConstants.ASSIGNEE
import com.onresolve.jira.groovy.user.FieldBehaviours
import static com.atlassian.jira.issue.IssueFieldConstants.*
import groovy.transform.BaseScript

@BaseScript FieldBehaviours fieldBehaviours

def issueManager = ComponentAccessor.getIssueManager()
def issueService = ComponentAccessor.getIssueService()

def selectedIssueType = getIssueContext().getProjectObject().getKey()

def issueType = getFieldById(getFieldChanged())
def optionsManager = ComponentAccessor.getOptionsManager()


def instance = getFieldByName("Instance")
def selectedOption = issueType.getValue() as String

def desc = getFieldById("description")
def descValue = "test desc"

switch (selectedOption) {

case "Epic":

instance.setRequired(true)
desc.setFormValue(descValue)
break

case "Story":

instance.setRequired(true)
desc.setFormValue(descValue)
break

break
}

 

This code does not work, if I change issue type, nothing changes

1 answer

1 accepted

0 votes
Answer accepted

Hi @gabe vid 

Behaviours are based on combination of project and issue type.

This page has information about it.

What exactly are you trying to do in your code? Make the instance field mandatory when Issue Type is either Epic or Story? For which project?

Ravi

Yes, that's what I'm trying to do

The project is selected in the behaviour "Mappings"

I need to do so cause I want the fields to be mandatory even in case you change the issue type of an old issue to the Epic or Story ones

Hi @gabe vid 

Try this code to make Instance field required when Issue Type is either Epic or Story.

def issueTypeValue = getFieldById(getFieldChanged()).getValue()
def instanceField = getFieldByName("Instance")

switch (issueContext.issueType.name ) {

case "Epic":
instanceField.setRequired(true)
break
case "Story":
instanceField.setRequired(true)
break
default:
instanceField.setRequired(false)
break

}

I hope it helps.

Ravi 

Like gabe vid likes this

Great, it worked this way.

@Ravi Sagar _Sparxsys_ 

Hi Ravi,

The script works fine at the time of creation of issue. But when i am trying to edit an Existing Issue and then changing the "Issue type" the custom field does not becomes mandatory or non mandatory.

I have placed the same script in the Server Script for the field "ISSUE TYPE" but it does not seems to be working

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events