Can JEMH be restricted to use just one project

I have a project called SUP (Support). I've configured JEMH to create/update issues in that project. And that portion works fine.

I have a second project, lets called TEST (My Test Project). This is a standard project and is not used by JEMH at all. Completely separate.

When email is sent to, the ticket is created in SUP, as it should.

When an email is sent to, and the subject contains something like "This is broken in TEST-200". JEMH then processes it and adds a comment on issue, TEST-200. As it is supposed to.

The problem is, regardless of what the subject line contains, I want the issue to be created in SUP (or the comment added to SUP - as appropriate).

I've added a Mapped project in the Configuration section of my profile.
I'v added a email domain mapping, for, and set the "Match again the addressee" flag.

The problem is that the comments are getting added to the other project.

Is there a way to restrict my JEMH profile so that ONLY the SUP project is being used. Regardless of what is in the subject line or anywhere else in the body of the email.

1 answer

1 accepted

Theory goes thats easy enough, there is an Email > PreProcessing > Subject IssueKey (comment) Regexps field that can be defined as:


This would then only map replies matching SUP-123 format rather than TEST-100?

Thats not quite what I want though. Still want the email that has the "TEST-100" in the subject line to get created in the SUP project as a new issue. Basically if the subjet line does not contain a valid "SUP-123" key, then create a new issue.

Although I may be able to work with what you have provided here though.

I see your variance and raise you a capture group:


This will then match on the first part matching SUP-123 if present, and if not, the second, which is any ABC-123. This means SUP references take priority for commenting purposes, which is what you want?

Fold! You win. :) I think that is exactly what I needed. Thanks

pls tick answer as correct if this workes for you?

Actually, sorry, the capture group above would then match only the 'first' match, probably not what is intended, to fix this, Ive CSV enabled the field, allowing order to be defined so...


... will then achieve what you want as each regexp will be tested indivudally. This will go into JIRA 6.1 compatible 1.5.8, and backported into 5.2.3+, 6.0.x builds also

available in 1.3.61, 1.4.39 and soon 1.5.8

Suggest an answer

Log in or Join to answer
Community showcase
Jason Wong
Published yesterday in Agility Beta

Welcome to agility

Every team in the world is unique, and so   Atlassian believes   that each and every team's best way of working  needs to  be molded to their unique circumstances  – ...

239 views 5 14
Read article

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