I am migrating an old JSD project from on-prem to the cloud and when going in I see warnings about the use of legacy automation, and how we should be using the regular Automation for Jira.
Is there a way to auto-convert old rules? If not, is there a simple how-to guide for creating new rules?
Hi Rob,
That is a very good question. At one point I recall understanding that Atlassian was going to automatically convert Legacy automations. However, I was scratching my head a bit on how that would actually work and I haven't heard any progress on that for over a year. I have been meaning to go in and convert the handful of legacy automations I had in place but I just haven't taken the time to do it. I think that the conversion is going to be so dependent on your specific automations that there isn't a one-size-fits-all answer here. What I would do, and what I plan to do, is to check the library for available templates that can be leveraged as a starting point when converting automations. I plan to start with "Easy stuff" and leave the challenging stuff to last. For those I will post here so you can help me! LOL!!
In all seriousness, if you have some specific ones that you can't quite work out please post them here and I'm happy to give it a go myself.
Hi @Rob Horan
thanks for your question.
Unfortunately, there is no way to convert legacy JSM automatically.
I'd suggest raising this with https://getsupport.atlassian.com/ though.
Cheers,
Maksim
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.