How to throw exception in Jira UI if some condition is satisfied in groovy script

shashank vivek

Although I can see error in catilina.out of JIRA but I want the user to stop making such change (psd < srsd) in case he tries to something like that. 

import com.atlassian.jira.ComponentManager
import com.atlassian.jira.issue.Issue
import com.atlassian.jira.event.issue.AbstractIssueEventListener
import com.atlassian.jira.event.issue.IssueEvent
import com.atlassian.jira.project.Project
import com.atlassian.jira.workflow.WorkflowException


public class Pdrtst_test extends AbstractIssueEventListener {
	@Override
	void workflowEvent(IssueEvent event) {
		this.customEvent(event)
	}
	@Override
	void customEvent(IssueEvent event) {
		Issue issue = event.issue 

	ComponentManager componentManager = ComponentManager.getInstance()
	def customFieldManager = componentManager.getCustomFieldManager()

	def cf1 = customFieldManager.getCustomFieldObjectByName("Prod Scheduled Date")
	def psd = issue.getCustomFieldValue(cf1)

	def cf2 = customFieldManager.getCustomFieldObjectByName("SIS Tech Review Start Date")
	def srsd = issue.getCustomFieldValue(cf2)

	if (psd < srsd){
		invalidInputException = new InvalidInputException("customfield_id_10491","Prod Sch date should be greater than SIS date")
		}
	}
}

I have put this script in script-listener and have set its Event as All events.

How can i achieve this ?

I want to show error on JIRA UI and stop user from making such change .

Jeremy Gaudet

A listener can't generate an error in the UI, as it doesn't come into play until after the triggering event is fired (which means the user has already successfully completed their edit in the UI such that the "Issue Updated" event is fired, for example). Using a listener, you could email the user and tell them they did something wrong; otherwise, if the change is taking place on a workflow transition, you can add a validator. If not, then perhaps the behaviors plugin can be used to add a validation to the field, but I've never done that so don't have any samples. You could restrict editing the field to a workflow transition, even if one that returns to the same state, as a worst case; from there, you remove the field from the general edit screen, and only include it on a screen presented during that transition.