def issue = ComponentAccessor.getIssueManager().getIssueByCurrentKey
def customField = ComponentAccessor.getCustomFieldManager().getCustomFieldObject(10731L);//customfield id
def appt = getFieldById("customfield_10729")
if(issue.getCustomFieldValue(customField) =~ 'JIRA')
We use the above script. In the above code the validation works with existing issue " DC_CM-1893".
Whereas we need to use the behaviour for current issue in create screen.
Not able to get the current issue key and apply validation.
Instead of existing issue we need the current issue which is about to create.
Please let us know how to achieve this.
Thanks Nic Brough,
We usually do hides the fields according to the other field values. There we don't need to mention the issue key, and it is taking automatically, whereas for the cascading select the same logic is not working. So we tried in the above script where we need the issue key.
This below script is working for normal select list and text field, but not for Cascade select list.
def Virtual = getFieldByName("Virtual Team") def prcd = getFieldByName("Proof of Concept Driver") log.debug("Virtual" + Virtual.getValue())
if (Virtual.getValue() =~ "Product Path")
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs