JEMH Project mapping is unable to find Project

Hi,

My requirement is to create a issue to a project based on the TO address of the email. SO i created project mapping and everything is working but, when i run the test case, it is showing the above error and creating the issue to the fallback project.

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

<dl><dt>Provided Value</dt><dd>430</dd></dl><dl><dt>Valid Values</dt><dd></dd></dl><dl><dt>Exception Stack</dt><dd><small>IssueProcessingException: 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) </small></dd></dl><dl><dt>Significant?</dt></dl>

Here '430' is the Project key.

If created a seperate profile for the projects, then the issues are creating for all project.

1 answer

1 accepted

Hi, just getting to this after summit. So, JIRA 6.1 does not allow a numeric project key, you get:

You must specify a unique project key, at least 2 characters long, containing only uppercase letters.

Is this a legacy project?

Btw, there is a checkbox in the Project section: Project Auto Assign if you set that, the address will be scanned as a project key automatically, it may just work (I cant test right now as I can't create a project with a numeric key).

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

2,988 views 12 18
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot