Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

JEMH with distinct Project mapping profile is not able to create issues

Pandu Ranga February 9, 2015

Hi, 

      JIRA Version: 5.2.11

      JEMH Version: 1.3.70

      I configured multiple properties for one profile using Domain Mapping.

JEMH Profile.jpeg

 When i am testing this profile using test case. I am getting the below error.

Insufficient valid information was found, no issue was created.

Provided Valuereporter=sbyrne, project=99, Reminder Date=09/25/2013, priority=Elevated, issueType=Work Memo, assignee=sbyrne, comment=some text, Testing,
Valid Values
Exception Stack
Significant?CAUSED REJECTION



Unable to process field [project], its not a Project key or numeric ID. Falling back to defaults to find a project for the issue.

Provided Value169
Valid Values
Exception StackIssueProcessingException: fixupProject: com.javahollic.jira.emh.engine.IssueProcessingException: fixupProject at com.javahollic.jira.emh.engine.FieldProcessorFixer.fixupProject(FieldProcessorFixer.java:2494) at com.javahollic.jira.emh.engine.FieldProcessorFixer.fixup(FieldProcessorFixer.java:177) at com.javahollic.jira.emh.module.fieldproc.AbstractFieldProcessor.fixup(AbstractFieldProcessor.java:324) at com.javahollic.jira.emh.module.fieldproc.BasicMailProcessor.getFieldMaps(BasicMailProcessor.java:51) at com.javahollic.jira.emh.service.ProcessorRunner.runProcessor(ProcessorRunner.java:710) at com.javahollic.jira.emh.service.ProcessorRunner.execute(ProcessorRunner.java:321) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerImpl.handleMessage(EnterpriseMessageHandlerImpl.java:247) at com.javahollic.jira.emh.ui.action.JEMHTestCases.doRun(JEMHTestCases.java:246) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70) at webwork.util.InjectionUtils.invoke(InjectionUtils.java:56)
Significant?



Insufficient valid information was found, no issue was created.

Provided ValueThe following values were provided, check validity:project: FOUND (99), reporter: FOUND (sbyrne), issueType: FOUND (Work Memo), summary: FOUND (null),
Valid Values
Exception Stack
Significant?CAUSED REJECTION



Unable to process issue, the exising configuration does not allow this issue to be created, detail: No project could be determined for the new issue, check defaults and addressing.

Provided Value
Valid Values
Exception StackIssueProcessingException: getIssueObject(): com.javahollic.jira.emh.engine.IssueProcessingException: getIssueObject() at com.javahollic.jira.emh.engine.FieldProcessorMapHandler.getIssueObject(FieldProcessorMapHandler.java:95) at com.javahollic.jira.emh.service.ProcessorRunner.runProcessor(ProcessorRunner.java:729) at com.javahollic.jira.emh.service.ProcessorRunner.execute(ProcessorRunner.java:321) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerImpl.handleMessage(EnterpriseMessageHandlerImpl.java:247) at com.javahollic.jira.emh.ui.action.JEMHTestCases.doRun(JEMHTestCases.java:246) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70) at webwork.util.InjectionUtils.invoke(InjectionUtils.java:56) at webwork.action.ActionSupport.invokeCommand(ActionSupport.java:433) at webwork.action.ActionSupport.execute(ActionSupport.java:157) at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:82)
Significant?CAUSED REJECTION



The project specified by the field [project] could not be found

Provided Value99
Valid Values
Exception StackIssueProcessingException: configureProject: com.javahollic.jira.emh.engine.IssueProcessingException: configureProject at com.javahollic.jira.emh.engine.IssueCreationHelper.configureProject(IssueCreationHelper.java:321) at com.javahollic.jira.emh.engine.IssueCreationHelper.getIssue(IssueCreationHelper.java:103) at com.javahollic.jira.emh.engine.FieldProcessorMapHandler.getIssueObjectViaCreation(FieldProcessorMapHandler.java:115) at com.javahollic.jira.emh.engine.FieldProcessorMapHandler.getIssueObject(FieldProcessorMapHandler.java:91) at com.javahollic.jira.emh.service.ProcessorRunner.runProcessor(ProcessorRunner.java:729) at com.javahollic.jira.emh.service.ProcessorRunner.execute(ProcessorRunner.java:321) at com.javahollic.jira.emh.service.EnterpriseMessageHandlerImpl.handleMessage(EnterpriseMessageHandlerImpl.java:247) at com.javahollic.jira.emh.ui.action.JEMHTestCases.doRun(JEMHTestCases.java:246) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at webwork.util.InjectionUtils$DefaultInjectionImpl.invoke(InjectionUtils.java:70) at webwork.util.InjectionUtils.invoke(InjectionUtils.java:56)
Significant?CAUSED REJECTION

Am i am doing anything wrong in the configuration?

Please help us to resolve this issue.

 

Thanks,

Pandu Ranga T

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

Post a new question

0 votes
Andy Brook
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 9, 2015
Unable to process field [project], its not a Project key or numeric ID

It looks like '99' is not a valid project name?

If thats not it, probably best to log a support ticket @ https://thepluginpeople.atlassian.net/browse/JEMH where I can better work on your problem.  Please attach your Profile XML and an email test case exported from JEMH auditing (not a .msg file).

Another source of the problem is:

  • the sender of the email does not have sufficient privileges to create an issue in the project
  • if the sender is an email-only user, the profile does not have defined a User > Default Reporter
TAGS
AUG Leaders

Atlassian Community Events