Hi Mehran,
To change that URL, take a look at https://documentation.riada.se/display/NAFJ/Set+up+your+own+Email+Template where you can set the type from JSD Details Type, to Details Type instead.
The difference is that one is used for the customer, so that they can acces their ticket, but the one you're referring to is for the agents, that can browse the tickets in Jira.
2. I have created a bug report for this, as URL encoding should be used and not HTML encoding. It's available at https://jira.riada.se/browse/NAS-55
Best Regards
Alexander
Hi Mehran,
A follow up question, what is the use case for when you get ((&)) in the URL ?
As I can see, we don't change the values for & signs, but they should now be sent just as they are, meaning & is not changed. However, if you might use a placeholder, and that value contains ((&)) it might happened.
Does your endpoint support & signs?
Best Regards
Alexander
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
dear alexander
thanks for your support my email problem solved , but still problem with & exist .
sms gateway use & to separate different part of url like mobile number and template id but when i sent jira field ( ex: ${summery}) and it contain &
trouble begins because sms gateway think it is other part of template and don't send any value after & , could you please help me in this regard?
BR
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Since we acquired NAFJ from Riada, the above link no longer works. Please use https://atlasauthority.atlassian.net/wiki/spaces/NAFJ/pages/930381840/Set+up+your+own+Email+Template
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.