Setup: mail-profile for incoming mails. matches against addressee to get the project, like jira_request.PROJECT@domain.com All the sudden this stopped working, resulting in rejections with the following hints: Hint #{0}: Provided Value Valid Values Message 1n/an/a Detail Unable to process issue, the exising configuration does not allow this issue to be created, detail: No issueType could be determined for the new issue, check defaults. Cause Caused By Caused rejection com.javahollic.jira.emh.engine.FieldProcessorMapHandler.getIssueObject():97class : com.javahollic.jira.emh.engine.InsufficientInformationException No issueType could be determined for the new issue, check defaults. Yes 2The following values were provided, check validity:project: FOUND (BF), reporter: FOUND (cju), issueType: FOUND (Projektleitung), summary: FOUND (null),

Really strange... but step by step: * only one issue type name Projektleitung [check] * issue type available in project [check] What seemed to have fixed the problem: change default issue type, change again to Projektleitung. For now it is working, but my confidence with JEMH is rather shaken :/

The only thing that I can see being a problem here really is that the issue type JEMH has is not valid for the project. A duff summary, project or reporter would give you another error. Can you check the full list of issue types and check that you definitely have only one that is even vaguely like "Projektleitung"? Also, could you try editing the JEMH handler - change the issue type to another one in that project, send it an email and then put it back the way you found it?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

issue creation by mail broken

Christian Juny

Setup: mail-profile for incoming mails. matches against addressee to get the project, like jira_request.PROJECT@domain.com

All the sudden this stopped working, resulting in rejections with the following hints:

<th>Hint #{0}:</th><th>Provided Value</th><th>Valid Values</th><th>Message</th>

n/a

<th>Detail</th>

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

<th>Cause</th> <th>Caused By</th> <th>Caused rejection</th>

com.javahollic.jira.emh.engine.FieldProcessorMapHandler.getIssueObject():97

class : com.javahollic.jira.emh.engine.InsufficientInformationException

No issueType could be determined for the new issue, check defaults.

Yes

The following values were provided, check validity:project: FOUND (BF), reporter: FOUND (cju), issueType: FOUND (Projektleitung), summary: FOUND (null),

Accepted answers

All comments

Christian Juny

I have to add, that the mail containsw a summary.

Original Email:

<th>Subject:</th> <th>Sent Date:</th>

mail test

2014-03-17 14:30:01,000

.....

Christian Juny

so why does the issue creation fail all the sudden?

Nic Brough -Adaptavist-

Your mail handler has been configured to create a certain type of issue in a certain project (when it can't match the incoming email to an existing issue)

However, you've configured that project to NOT have that type of issue in it. So the mail handler cannot create the right issue type. So it dies.

Christian Juny

But the project has the issue type in question. I can create those just fine in Jira, but not via mail. And your answer does not explain why it says there is no summary, which would seem to be the problem for the mail handler here, is it not?

Nic Brough -Adaptavist-

JEMH is telling you that the issue type you have configured it for cannot be created in the project.

You need to check both ends as well - it might be that JEMH is configured to create type X, but you've got type Y in the project with a similar-but-not-the-same name/id.

The summary doesn't seem to have anything to do with it, and you haven't menteioned "no summary" in your question, so I didn't know you wanted me to talk about that (even though it's irrelevant because the problem is with the issue type)

Christian Juny

I see that it is telling me that, I just don't get why.

We have only one issue type with that name mapped as default for this jemh-profile. Hint 2 names it "FOUND (Projektleitung)". So I'd tend to rule out the suggested X-Y-missmatch.

What am I missing? What would be the other end, since you suggested checking "both ends"?

unknown

Please always check for updates, when bugs are found, they are fixed as fast as possible and new releases made. There was a bug located yesterday in 1.5.47 which was fixed in 1.5.48, released yesterday.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration

jemh

addon-com.javahollic.jira.jemh-ui