Sending email from Jira Service Desk as a functional name ("Acme Support")

[Greg Johnson]

Our JSD customer notifications are being sent from

"Agent Name" <support@acme.com>

where "Agent Name" depends on which agent responded.  We want to present instead as:

"Acme Support" <support@acme.com>

but cannot find any kind of setting for this, nor mention of it.

Any ideas, wisdom of the universe?

[Angélica Luz]

Hi Greg,

Currently, it's not possible to edit the "Email From" in notifications.
We do have a feature request suggesting the implementation of such ability:

- https://jira.atlassian.com/browse/JSDCLOUD-702

Please, make sure to watch and vote to receive updates about the feature.

I'm sorry we can't be more help on this at this time.

Regards,
Angélica

[Greg Johnson]

Hi Angelica,

Thanks for the reply.

Is there a difference between an issue for Jira Service Desk Cloud and Jira Service Desk Server?  It seems like there is a big disparity in UI and underlying features.

Where is the roadmap of features that will be implemented in the next release (not just our wishlist :-)?

Sorry about all the questions!

Cheers,

greg

[Angélica Luz]

Hi Greg,

There are some differences between Jira Cloud and Server.
Jira Cloud has many restricted functions, but, for example, the feature I sent you does not have on Jira Server as well.

You can find the Pros and cons of Cloud vs Server on the link below:

Atlassian Cloud vs Server apps

To find out what features are being implemented, you can check our "What's new" that shows the updates each week:

Atlassian Cloud Documentation blog posts

Hope this helps!

Regards,
Angélica

[Paul Stallworth]

@Angélica Luz do you have any suggestions on how we could workaround this for JSD Server, like even some deep technical hacking?  This is a daily issue for us as I mentioned on my comment on https://jira.atlassian.com/browse/JSDSERVER-702.  Something as simple as hacking up the Email from for JSD notifications would eliminate so much confusion for our users.

[Angélica Luz]

Hi Paul,

There is no workaround for this feature yet.
We must wait for our dev team to implement this feature in future releases.

Regards,
Angélica