How to use custom field Sprint in email handler

[khushboo_puri]

How to use sprint custom field in email handler?

@Sprint= ???

It is a locked custom field

[Mirek]

Hi @khushboo_puri 

What exactly you want to to with this Sprint field? Do you want to parse sprint ID/Name and put an issue directly to it once it is created by email? Are you using any plugins/extensions for that? 

Could you please clarify? 

[khushboo_puri]

Hi @Mirek 

We use JEMH to populate the fields through email like @Issuetype= story. Similar way we want sprint value to be filled through email. Issuetype is a system field but sprint is a locked custom field. Do I need to do any configuration on JEMH to autopopulate sprint value?

[Ryan Clifton]

Hi @khushboo_puri 

Based off the information you have provided, it appears that you are attempting to use the At Prefix Field Processor to set the Custom Field values.

It is possible to set the Sprint field using the At Prefix Field Processor, however you would need to provide the directive with two values (the Board Name and the Sprint Name) using the same format as below:

@sprint=Board Name:Sprint Name

More information about doing this see the "#2 - Directives" section on the following page: Automatically assign new issue to a sprint

If you require any further help, then feel free to create a support ticket with The Plugin People (JEMH Vendor) support. This can be done by emailing "support@thepluginpeople.com" or by using our Portal.

Regards,

Ryan (PPL Employee)

[khushboo_puri]

Hi @Ryan Clifton @,

I tried above suggestions but with sprint it's not working, Sprint is a locked custom field, is it a problem?

[Ryan Clifton]

Hi @khushboo_puri

The fact that the Sprint Field is locked, should not prevent JEMH from setting the field. As currently the field being locked only prevents you from changing the name/description of that Field. 

I see that you have created a Support Ticket, if possible could you please attach a JEMH Support zip to the Support Ticket. As this will provide with additional information which we can use to review further.

Regards,

Ryan (PPL Employee)