Hello all,
For starters, I'm very new to Jira, trying to help out the admins with automation and I've hit my first major roadblock.
The short version is.. we have a field that is supposed to house a URL (manually entered), and then the automation is supposed to call on that field and put its data into an email that is sent when the ticket is moved between statuses. We are using a custom field (customfield_11524) which I've confirmed is correct via the XML for the page. In my automation, it's being called by the following:
<a class="link" href="{{issue.customfield_11524}}">Peer Review Document Link</a>
The URL in the field is https://www.w3schools.com/html/tryit.asp?filename=tryhtml_color_text (we just used that to test). When I open the link on my computer, it opens just fine. However when we move the issue between statuses, the email generates and the URL appears as a single period (.). Interestingly, if I put a different URL in there (https://www.google.com) and move to a different status, the email generates and the link works.
What I'm wondering is.. why does the first link not work, but a different link does? I'm assuming it has to do with the ? or the = in the link but I'm not sure. If someone could provide some insight, I'd really appreciate it! Thank you!
Greetings! It would be helpful if you could share a screenshot of the Automation rule in this regard.
Hello Mariano,
Thank you for the response. The relevant screenshot is below. Hopefully this helps!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the community.
I suspect customfield_11524 is a field of the type URL, if so you can just use the following in the email body.
{{issue.<customfield-name>}}
If the field is not a URL field, but a text field, you can use:
<a href="{{issue.toUrl}}">{{issue.<customfield-name>}}</a>
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Marc,
Thank you for your response.
According to the XML, it is a URL field - Sorry, I forgot to paste that in the above message. This is how the XML reads:
If I'm reading that right, it should be a URL field. Since I was able to put in a different URL and it worked, I think it's something specific with this URL that is the issue, I just don't know exactly what that issue might be. At this point, I'm just trying to head off future issues, for when someone inevitably puts something in there like this and possibly causes an issue.
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.