create projects with an email handler

Andre April 17, 2013

We just starting using Jira as a task manager for technical support of our products. The task's / issues should be collected project oriented (there are different issue types, every with its own workflow).

To get the project names synchronized with a enterprise resource planning system we have to find a way booth systems can interact. I think the easiest way is a suitable mail handler inside Jira.I did not find a solution for it!

My question: Is there a plug in or something similar to get this done or do I have to implement a plug in for Jira?

Thanks in advance!

2 answers

1 accepted

1 vote
Answer accepted
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 17, 2013

No, you'll need to write something.

I suspect this is because it's a potential disaster, and quite complex. Creating a project requires a whole batch of configuration, and, if you did it by email, what happens if someone sends you 30 emails? You sure you want 30 projects? There's a lot of coding to be done, and I suspect it far outweighs the cost of having your admins set up a handful of projects manually.

Of course, you should then use email to create, comment and do more with the issues within the projects (And look up the JEMH plugin - always worth investigating when email and Jira are mentioned in the same breath)

Andre April 17, 2013

Wow what a fast answer! Thank you very much!!!...

OK, understand. I undervallued the configuration to be done when create a new project. I thought some template could be used in this case. If I understand correct this all has to be done by the plug in.

I'll check out the JEMH plugin and try to think about other ways to handle it!

Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
April 17, 2013

If you set up your defaults relatively baselined (i.e. optimised for the projects you want to create from the other system) , then you could minimise the work you need to do in any plugin/script etc. Have a quick look at the "add new project" screen to see the basics of what a project needs to be set up.

Andre April 18, 2013

I already created some project's and checked the needed set up. I'm aware about the consequences of my request. For now I will proceed creating projects manually, checking plug in's like "project generator for Jira" to make my work more efficent. If I'm more experienced with Jira and there is no other way for our company I'll refresh that issue. Thanks for forwarding to Andry Brook, know I know there is some one who could care about it when delivering proper information. Thanks!

0 votes
Andy Brook [Plugin People]
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.
April 17, 2013

Yea, I'd echo Nics comments. Its funny but I have recently added coding to support project creation, custom field creation and more but thats only during JEMH Profile restore, rather than in the processing of emails.

For such a hypothetical project creation, there is a lot to consider:

Name, Key, Description, Logo, ProjectLead, Components, component owners, notification scheme, permission scheme, workflow....

Sure you could nominate a template project to cover off notification, permission, workflow, but the others need specifying.

JEMH has a Directive mechanism that allows users to change how and where an issue is created, as yet, there isnt anything to do that automatically.

If you can expand on how your emails get generated (how the content would be made consistent) perhaps I can see how to do this.

I could envisage something like:

@autocreate.project.template=XYZ

@autocreate.project.key=ABC

@autocreate.project.name=Name

@autocreate.project.components=component 1,component 2, etc

As you can see there would be a lot to say....

Suggest an answer

Log in or Sign up to answer