Using JEMH, how can I set a default issue type per project

I have a very simple setup where the users enter the project key in the subject line of email to route to the right project. I have a fallback project, CHG with a fallback issue type, "Change". But, if user specifies project (ABC) in their subject line, and project ABC has no such issue type as "Change", then their issue is posted with type = "Bug", the global default. This issue type makes no nsense for Project ABC, and I need it to be "Update". What I need is to specify a separate default issue type for each project. I don't want users to have to add directives. Is there a way to do this either in Jira (5.2) or JEMH (latest)?

1 answer

1 accepted

1 vote
Accepted answer

Aha. The behavior I was seeing was because my issue type scheme in project ABC did not have a default issue type. Once I set one, it seems that now the newly created issue defaults to the default issue type for the scheme, and not the global default.

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted yesterday in Agile

What is Scrum? A good, bad, and ugly answer.

In a world of dark-scrum, faux-scrum, and scrum-butt, the question still remains: What is scrum and how do you do it “right?” That’s the question we set out to answer. I'm Max, I've been teaching c...

78 views 0 4
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