JIRA email interface

[Marek Sapota]

I'm integrating Phabricator (to be precise Differential code review tool) with JIRA issue tracker. I'm using JIRA email interface for the integration and I'm finding the documentation insufficient.

1. When sending comments by email, what is actually needed for JIRA to figure out which task is being commented? I've read that the issue ID would be sufficient but it didn't seem to work. Currently I'm using '[jira] TASK-ID' in the title which works but I'm curious if '[jira]' is really needed there.

2. When uploading patches to Apache Foundation instance of JIRA you can assign copyright to Apache. Is it possible to do that using attachments and the email interface?

[Wojciech Seliga · Accepted solution]

Ad 1. If I undestand you correctly you use CreateOrCommentHandler, right? If yes, then try switching on full debug info for this class (logger for package com.atlassian.jira.service.util.handler). Normally this handler looks for the valid issue key (the first key which points to the existing issue stops this process) in mail subject. As a fallback it tries to find issue key "In-Reply-To" header. If none of them succeeds then it creates a new issue instead of adding a comment on existing one. If this info + what you get from debug stream will not help you, then take a look at com.atlassian.jira.service.util.handler.CreateOrCommentHandler#handleMessage method.

Ad 2. Apache uses a special plugin which adds a field (flag) to every attachment. JIRA does not provide it out of the box. You would need to craft similar plugin or take a look at https://plugins.atlassian.com/plugin/details/27524

[Marek Sapota]

1. Thanks, that should be helpful.

2. Thought it was JIRA built-in, thanks for clarifying.

[Nic Brough -Adaptavist-]

I'm not familiar with question 2, but for 1, all it needs is the human issue id. The PROJECT-NUMBER combination (I'm spelling that out because "issue ID" is not a great phrase to use in Jira world - every issue has two unique things which could be called "issue id", so I try to be clear. The technical issue-id in the database is a simple number, which never changes. The human issue-id is the project-number string which can change). In other words, yes, you can drop the [jira], all your email should need is task-id

[Marek Sapota]

I tried with only PROJECT-NUMBER and JIRA just drops the email then.