Scripted Field vs Listener - Which is better to use?

patricia_scott_honeywell_com

I have a feature I want to add, but see that I could implement this using either the ScriptRunner Scripted Field, or Listener.  I am not sure how to determine which would be the better feature to use.  This is what I am doing.

For issue type A, B and C, when an issue is updated/created, I want to retrieve the Priority and Created Date.  Based on the Priority, I want add a certain number of days to the Created Date, and set the new date in the New Date field.  The New Date field is not editable by the users, read only so only on the View Screen.

For example:

- If the Priority is "Critical", I add 2 days to the Created Date, then update the New Date field with that date. 

- If the priority value is changed to "High" (Or any other priority value), then the New Date is recalculated and updated.

I have already implemented this using a ScriptRunner Listener and configured the listener to only be for certain projects and issue types and on the Create/Update events.  All works perfectly.

However, I believe I can implement the same feature by using a Scripted Field?

My question is, are there any pros/cons with doing it with either Scripted Field or Listener that I should consider before choosing which approach to use to implement this in our production environment?

Nic Brough -Adaptavist-

Ok, so I'd rule out a Behaviour straight away - they act on the front end, and although you could use them to default a date into an enterable field on create or edit, the users would be able to override it, and if they edited the priority it wouldn't update.  There are also ways they could edit that Behaviours can't intercept, which again would let them break it.

A listener is a good option because it can catch every change and re-calculate your field if necessary.

But, yes, a scripted field might be an even better answer - it's easier to code for, puts less load on the system and doesn't mean your admins have to think about when it is being triggered or remember to never add it to a create or edit screen.

The only thing I would want to make the choice on is how a read-only date field works on screen for your users.  Scripted date/time fields look a little different to standard custom date fields.