Changing an issue status with Email

Hi

we have customers who are using Jira as well and I am Trying to synchronize both Jiras.

Creating and Assigning Issues throuth the Email has worked.

Is there anyway to resolve or close Issues through Email: what I want is that as soon as an Issue in our Jira is closed, the correspondent Issue by the custemers closes as well.

Will be very thankfull for any solutions.

Kind regards

Irina

2 answers

0 vote
Henning Tietgens Community Champion May 14, 2013

You could use the JIRA Enterprise Mail Handler plugin for transitioning issues through emails.

Henning

Hi Irina,

Can you explain a little more how the two JIRAs' are related? Does one drive the other?

If you have two JIRA's and you are trying to do any kind of synchronization, JEMH and Sync Agent for JEMH could help. It supports replication of issue creation from 'A' to 'B', as well as bi-directional updates, comments and workflow, using just email.

How it works is that a SyncAgent in 'A' picks up all issue events in configured Projects, generates required XML payloads that are sent by email to a mailbox that a JEMH instance in 'B' picks up and processes. The email relates the remote issueKey, subsequent events are equally related. That issueKey is stored in a custom field in 'B', allowing future correlation.

Setting up Uni-Directional replication of issues from 'A' to 'B' would cause issues created within projectX @ 'A' get replicated to projectY in 'B', updates and comments in 'A' get reflected in 'B'. With no Bi-Directional configuration, changes or comments in 'B' do not come back to 'A', workflow changes in 'B' do not get propogated either.

That 'A' has a different workflow to 'B' is handled by Sync Agent that can configure a per-event custom workflow action. (NOTE: A problem with any worklow management is that if the remote 'B' issue is not in a valid state for the transition, then the workflow step will fail. Presuming that 'close issue' will always work)

I'm not entirely sure how much or little you want to synchronize as the question is only concerned with issueStatus, as maintaining the relationship between one issue and another is core to the problem.

Other solutions may well exist or can be coded as custom solutions.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,325 views 14 20
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
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