Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Fails to update field using JEMH

Michael Danielsson
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 18, 2013

Hi

I have problems updating a field in Jira by using JEMH after update of Jira and JEMH to the lastest version.

The log says:

2013-02-18 14:45:34,657 QuartzWorker-0 DEBUG [jira.emh.processor.AtPrefixedFieldProcessor] Got unknown key, possibly a Custom Field: 'cloned issue id' = PPP-TR-901
2013-02-18 14:45:34,701 QuartzWorker-0 DEBUG [jira.emh.processor.AtPrefixedFieldProcessor] Fields Found:
2013-02-18 14:45:34,701 QuartzWorker-0 DEBUG [jira.emh.processor.AtPrefixedFieldProcessor] Key: cloned issue id = PPP-TR-901
2013-02-18 14:45:34,775 QuartzWorker-0 DEBUG [emh.engine.support.EMHCustomFieldHelper] Checking issue CF [Cloned Issue Id, type=Read-only Text Field]
2013-02-18 14:45:34,775 QuartzWorker-0 DEBUG [emh.engine.support.EMHCustomFieldHelper] Processing directive [cloned issue id], CustomField match: Cloned Issue Id
2013-02-18 14:45:34,775 QuartzWorker-0 DEBUG [emh.engine.support.EMHCustomFieldHelper] Found the custom field: Cloned Issue Id
2013-02-18 14:45:34,775 QuartzWorker-0 DEBUG [emh.engine.support.EMHCustomFieldHelper] fIssue is null:false
2013-02-18 14:45:34,775 QuartzWorker-0 DEBUG [emh.engine.support.EMHCustomFieldHelper] fApplicableReporter is null:false
2013-02-18 14:45:34,776 QuartzWorker-0 DEBUG [emh.engine.support.EMHCustomFieldHelper] User [pcosynch] has permission [12] : true
2013-02-18 14:45:34,776 QuartzWorker-0 DEBUG [emh.engine.support.EMHCustomFieldHelper] Setting up custom field [Cloned Issue Id/com.atlassian.jira.issue.customfields.impl.ReadOnlyCFType], emailProvidedValue: [PPP-TR-901]
2013-02-18 14:45:34,776 QuartzWorker-0 DEBUG [emh.engine.support.EMHCustomFieldHelper] Empty value given, clearing CustomField: Cloned Issue Id
2013-02-18 14:45:34,781 QuartzWorker-0 DEBUG [emh.engine.support.EMHIssueUtils] setupComplexCustomFields()
2013-02-18 14:45:34,783 QuartzWorker-0 DEBUG [emh.engine.support.EMHCustomFieldHelper] Processing directive [cloned issue id], CustomField match: Cloned Issue Id
2013-02-18 14:45:34,784 QuartzWorker-0 DEBUG [emh.engine.support.EMHCustomFieldHelper] User [pcosynch] has permission [12] : true
2013-02-18 14:45:34,784 QuartzWorker-0 DEBUG [emh.engine.support.EMHCustomFieldHelper] Setting up complex custom field [Cloned Issue Id/com.atlassian.jira.issue.customfields.impl.ReadOnlyCFType], emailProvidedValue/default: PPP-TR-901
2013-02-18 14:45:34,996 QuartzWorker-0 DEBUG [jira.emh.service.ProcessorRunner] Issue Processing Summary: Created 0 [], Updated 1 [PPP-MAINT-2999], Commented 0 []. Rejections required: 0
2013-02-18 14:45:35,002 QuartzWorker-0 INFO [jira.emh.service.EnterpriseMessageHandlerImpl] ProcessorRunner completed with status: canHandle
2013-02-18 14:45:35,025 QuartzWorker-0 INFO [jira.emh.service.EnterpriseMessageHandlerImpl] JEMH is telling JIRA to delete the email

Jira says:

PPP Synchronisation User removed the Cloned Issue Id of PPP-MAINT-2999 - Test of Synch

Does anyone know what the problem can be?

Regards,

Michael Danielsson

2 answers

1 accepted

0 votes
Answer accepted
Michael Danielsson
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 18, 2013

Hi,

The reason to my problems was that the "Cloned Issue Id" was read-only in JIRA and JEMH had changed behavior for this customfield type.

Now it is not possible to set a read-only customfield unless it is empty.

Regards,

Michael Danielsson

0 votes
Andy Brook [Plugin People]
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 18, 2013

Hi Michael,

It looks like this field is being processed twice, perhaps unnecessarily. Can you confirm if the 'output of the email processing is correct?

To diagnose further, please create a support issue @ JEMH Jira and attach your JEMH Profile XML, and a JEMH Test Case email.

Thanks,

Andy

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events