Cierre de sprint

[Natalia Correa Sánchez]

El sprint al cerrarlo me dice que tengo cero incidencias cerradas por ende cuando creo el siguiente me lleva todas las incidencias y veo estas y si están en finalizadas. 

[Danyal Iqbal]

You cannot restrict the approver field by default. You need to explore a workaround. You can either create single/multi user picker which is automatically filled by a mapping (approver<>custoemr) in a groovy script and configure the notification scheme to send a notification to the users in this field or you can use the beahviours plugin to prepopulate the approver field.

[Reapit Service Desk]

thanks Danyal - forgive me, as Im not a Sys Admin type person (programmer a long time ago).  

With groovy / behavior plugin would that be able to choose the approver based on the organisation associated with the person raising the request ie 

Pers A Org X = Approver set to Bob

Pers B Org Y  = Approver set to Janet

This is an element that may stop me deploying JSD - Ive set the Customer permissions so they have to type in the exact email of the approver now (not great) as before they could see too much.  

[Danyal Iqbal]

With groovy / behavior plugin would that be able to choose the approver based on the organisation associated with the person raising the request ie 

Pers A Org X = Approver set to Bob

Pers B Org Y  = Approver set to Janet

Yes, for starters I would recommend 1 approver per organisation and prepopulating the approver according to the organisation. So basically, instead of typing out the exact email address of the approver everytime, you can prepopulate the approver from the reporter/organisation.

[Reapit Service Desk]

Hi - believe behaviour plugin doesnt work on cloud; so default would be Groovy for this.  Are there any 'examples' that would look similar to what I need to do, that i could life and work from .... cheers