Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
/
Issue workflow transition by email
Updated Jul 14, 2023

    Issue workflow transition by email

    This guide will show how an issue's status can be manipulated through email using JEMHC.

    Step-by-step guide

    1. With an example issue

    2. see what Workflow transitions are available:

    3. In this example, we'll use Close.  Navigate to the JEMHC Profile:

    4. Select Project Mappings (1), then edit the Default / applicable mapping (2):

    5. Then select Field Processors section (1) and edit it (2, drill down not shown), enabling Directives (commands) for Create and Comment (3), and the At Prefix Field Processor (the command format interpreter), (4):

    6. Validate that the Profile is correctly configured for email user interaction, it should reflect the issue custom fields:

    7. Now, create an example JEMHC Test Case:

    8. Select the Profile this Test Case will run against (1), then refer the issue key in the subject (2), set the address to match your inbound mailbox catchemail address (3).  The Directive for workflow transitions in the At Prefix Field Processor format is @workflow=transition (4).  If provided, a the remained of the email will be used as a comment (5).  Finally, submit the form to save settings (6):

    9. When saved, the new Test Case will be listed, run it!

    10. The Test case run results indicate the value was applied (I'll ignore the remove watcher thing for now )

    11. Looking at the issue, its closed!

    Changing the Resolution

    Yes, the resolution can be changed too with the @workflow.resolution=value, directive:

    MIME-Version: 1.0 Date: Sun, 19 Jun 2011 17:42:26 +1200 Subject: SUPPORT-505 From: user@faraway.com To: test@localhost Content-Type: text/plain; charset=UTF-8 @workflow=close @workflow.resolution=duplicate some comment

    Work in progress

    Full support for workflow transition properties that may be need have not yet been implemented.

    Related articles

    • Page:
      Approving requests via email
    • Page:
      Email notification mappings
    • Page:
      Configuring email only users notifications
    • Page:
      Directives
    • Page:
      Ad hoc notifications
    The Plugin People
    Teams
    , (opens new window)

    Enterprise Mail Handler for Jira Cloud (JEMHC)
    • Getting started
      Getting started
       This trigger is hidden
    • Documentation
      Documentation
       This trigger is hidden
    • Licensing
      Licensing
       This trigger is hidden
    • How-to articles
      How-to articles
       This trigger is hidden
    • Common Problems
      Common Problems
       This trigger is hidden
    • Support
      Support
       This trigger is hidden
    • Migrating from Server/DC to Cloud
      Migrating from Server/DC to Cloud
       This trigger is hidden
    • Frequently Asked Questions
      Frequently Asked Questions
       This trigger is hidden
    • General Data Protection Regulation (GDPR)
      General Data Protection Regulation (GDPR)
       This trigger is hidden
    Results will update as you type.
    • What is JEMH Cloud?
    • App documentation
    • How-to articles
      • Add recipients by Velocity script
      • Add/Remove (Custom) field to Jira/Service Management/Transport Desk Create Notifications
      • Exclude auto-replies
      • Create an email signature macro to be used in notifications
      • Create custom Theme and Templates
      • Detect that a Service Desk comment is private/internal
      • Diagnose outbound mail connectivity
      • Handle Wiki-Markup with Comment Only Body Delimiters
      • Handling signatures, replies and forwarded messages
      • How to use Directives to set a date time that is relative to a nominated time zone
      • How to verify comment visibility applies
      • Inhibit notifications based on run-time conditions
      • Install the Dashboard Gadget
      • Issue workflow transition by email
      • Logging a JEMHC Support Ticket
      • Notification Schemes and JEMHC
      • Understand how Issue association works
      • Use Aliases
      • Use Project Mappings
      • Use Priorities in Project Mapping Rules
      • Use Regexp Field Processor
      • Validate Mail Connections with Telnet
      • Opt-out of Google Analytics anonymous reporting
      • Integrate to Office 365 using Exchange Web Services
      • Understand How Project Association Works
      • How to generate acknowledgements for create and comment to the sender only
      • Forward an email to Jira as the sender
      • Set a default customer request type
      • How to export your profile
      • Changing the from: address used (statically or from a Custom Field)
      • Collect customer satisfaction feedback
      • Telegram Integration
      • Approving requests via email
      • Creating an outbound message connection
      • Forward notifications
      • Allow non-Jira (email-only) users to participate and be notified
      • How JEMHC Calculates Data Usage
      • Migrating from Data Center to Cloud
      • Support high outbound mail volumes
      • How Jira events turn into emails
      • Setting a custom field value
      • Send notifications via a SMTP Relay Service
      • Convert replies to sub task
      • How to use custom Directive Date Formatting
      • Determine non-business hours in Notification Templates
      • Prevent Mail Loops
      • Get notified via non-email connections when a message source/outbound goes offline
      • How-to grant JEMHC access (Project and Admin)
      • Creating Issues via Jira API
      • Test user lookup and Workaround User configuration
      • Differentiate Issues Created by JEMHC vs API
      • Using JSM Forms and Widgets
      • Using JEMHC in Jira with Third Party Systems
      • Customise the Content / Comment Header
      Calendars
    You‘re viewing this with anonymous access, so some content might be blocked.
    {"serverDuration": 9, "requestCorrelationId": "afda813303a2417cb958d6d83d5b0a31"}