"One questions that sticks out is versions. If a template that also has versions is duplicated would the expectation that the versions are also duplicated in the copy"

-- I think a toggle or checkbox for "Duplicate with versions" would be a nice clean approach.

"Additionally what if we surfaced a unique identifier for a template to effectively allow for sending of the template across any sending domain."

-- For me this would be extremely handy!

I love the idea of being able to send a template from any sending domain! Definitely gets my vote!!

For template copying, I don’t think I’d expect it to include the version history.

love the idea of using IDs instead of template names! names tend to have spaces

in the meantime, you can use this to copy a template:

https://github.com/toddhodes/mailgun-copy-template

going to see if i can adapt this

https://github.com/paliwalvimal/mailgun-template-migration

re: duplicating versions or not

just copying a single version is fine if that's easier for you guys to provide.

only a single version can be active anyway, so, versions aren't really useful for much except as backups. unless i am misunderstanding something.

eg, the challenge here is i make a template and then ask for variations on the theme, eg, specialized to different customer lists. these different versions cannot be used without carefully toggling which is "active"; one wrong move and the wrong email goes to the wrong list)

just need to be able to clone a template, edit it, and be able to reference it, "live"

Re: the latest reply - glad to hear it's in the queue!

For our pretty straightforward use case (use the same visual elements across a bunch of different emails, without recreating them each time), neither of those features would be particularly necessary. The version history wouldn't be super important, and we only use one sending domain.

Dear support team -
am I mistaken that it is NOT possible to copy an entire template within the same domain and e.g. take it as a basis for a language variation?
That would seem rather odd... and a very basic functionality...
>H

Yes, or the ability to manage templates outside of a domain's scope. If we could create a template and use it across any configured domain, it would solve the problem for me.

However, since this will likely never happen, simply having a copy feature would enable us to get the job done.

I cannot believe this feature is missing; its absolutely essential.

I can't believe this basic feature is not available in Mailgun.

can't imagine we still don't this must-have feature :(

This is such an essential feature - please, please, implement it. I use Mailjet too and there is that option, it would be great if it's exactly the same.

Please please make this available

It makes no sense not having this feature. It's essential.

This would be a fantastic addition!

Please guys implement this feature, otherwise there is no point to have a Template Email.

I agree not having this feature is ridiculous. I tried to use the API to do it, but it's also having issue.

I completely agree, templates are a complete mess without the ability to duplicate one

+1