Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Updated information about the first mail handler migration webinar

We’ll be holding our first webinar on the topic of mail handler migration a month before we stop providing access to creating new Classic mail handlers.

...

Join Zoom Meeting https://zoom.us/j/99601439747?pwd=RHJtRlpSYmsrdUF2YWVHUFF4UDVsUT09

Meeting ID: 996 0143 9747
Passcode: 851774
One tap mobile
+13017158592,,99601439747#,,,,*851774# US (Washington DC)
+13126266799,,99601439747#,,,,*851774# US (Chicago)

Dial by your location
+1 301 715 8592 US (Washington DC)
+1 312 626 6799 US (Chicago)
+1 346 248 7799 US (Houston)
+1 669 900 6833 US (San Jose)
+1 929 205 6099 US (New York)
+1 253 215 8782 US (Tacoma)
Meeting ID: 996 0143 9747
Passcode: 851774
Find your local number: https://zoom.us/u/afSapCQLw

Join by Skype for Business
https://zoom.us/skype/99601439747

...

  • why the Next-Gen mail handler is necessary and why the Classic mail handler will be deprecated

  • the key differences between the Classic mail handler and the Next-Gen mail handler

  • the main components of the Next-Gen mail handler and how they work

  • how to set up a simple Next-Gen mail handler for your Jira Service Management project

After a 30-minute video demonstration of the above points, you will have the opportunity to ask anything and everything about the topic and we'll do our best to answer them.
If you have a more complex question, need help with your own configuration or got stuck with the setup, please feel free to open a request on our customer portal and we'll investigate your options more in-depth.

With the next-gen handler’s success, we are slowly saying goodbye to our Classic mail handler (and the field rules along with it).

General information about the deprecation process

A detailed roadmap will be shared later on, but as of now the following steps are planned:

  • Creating classic handlers will not be possible in versions released after the end of Q2 2021. Existing ones will work and have the option to be edited or deleted, no new developments will be carried out on the classic handler.

  • In the versions released after the Q3 2021 creating AND editing handlers will be unavailable as well. Existing ones will work and have the option to be deleted, no new developments will be carried out on the classic handler, support is no longer available for this feature.

  • The Classic handler will not be available for use in versions released by the end of Q4 2021, editing and creating will both cease to exist, the function will have been deemed obsolete and will be taken out of the app as a whole.

...

As you can see, you still have time to convert your old handler to the new one and we’ll keep you updated along the process. As a part of this, we will try to reach out to our customers via the following platforms:

  • send you emails about the process

  • build info messages into our product so that you won’t be able to miss it

  • hold webinars until the release in order to help you make the transition

  • inform you of a more detailed roadmap later this month.

For essential information about the next-gen handler and a comparison between the two handlers, please see our documentation.

...

Expertisefinder redirect
forcedfalse
typeurl
dest{"value":"https://docs.meta-inf.hu/email-this-issue-for-jira-server-data-center/documentation/incoming-emails/phasing-out-the-classic-mail-handler"}
enabledtrue

Thank you for visiting our old product documentation site. Note that we no longer store or update our documentation here.
Please navigate to our new documentation site and update your bookmarks accordingly. If you're looking for the former content of this page, click here.