Hi everyone,
When users email into our JSM project, the ticket description sometimes includes very large Mimecast SafeLinks, such as: https://gbr01.safelinks.protection.outlook.com/?...
Is there a way to:
Any suggestions or best practices would be greatly appreciated!
Hi @Andrew
You could look into automation to have a rule based on issue creation, remove that information from the description field.
Hello @Andrew
Is there any specific reason why users are using that URL for the description? Regular expressions are only available for Jira forms. Speaking of forms does your project use forms?
https://confluence.atlassian.com/jirakb/using-forms-regex-validation-1255454685.html
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you @Nikola Perisic
The issue is with users emailing to raise a ticket (this is a requirement for our process). Our client uses Mimecast, which adds a security banner and a very long SafeLink
I initially tried trimming the message, but we discovered that some tickets are forwarded which means you lose the latest comment and the emails can contain multiple banners,.
What I’m looking for is a way to:
Detect and clean up Mimecast SafeLinks in the email body when the ticket is created.
Ideally replace them with a simple hyperlink (e.g. Click here) or remove them entirely. We can always go to the email log if we need to retrieve the link.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You could create an automation rule that for a condition will have JQL which will have a keyword of text followed by tilda sign.
text ~ your link would go here
This will scan whole issue containing any text. Then for the action you would select Edit work item, select Description and leave it empty which will clear it afterwards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.