Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Suggested knowledge base article smart value


We use Jira Cloud, and the Service Desk for internet ticketing.
When a user creates a ticket, three knowledge base articles are suggested.
More often than not, these are overlooked by the end user.

We want to create automation that sends an e-mail to the reporter containing links to these three suggested knowledge base articles.


I can, for the life of me, not find the smart value(s) needed to link/reference these articles.

What I've tried:

Digged through Atlassian documentation on smart values.

Installed JSONView plugin for my browser, and trawled through the data.

1 answer

1 accepted

2 votes
Answer accepted

So I enabled Chrome's Developer Tools and watched the Network tab when I entered "VPN help" into the Summary of a Service Desk request and saw this query pop up:

That returns a JSON result with the suggested results.

You would do this in Automation by using Web Requests, querying for  {{issue.summary.urlencode()}}

I think you could then send an email that contains the contents of those results, using something like:

* <a href="{{url}}">{{title}}</a>

Unfortunately that endpoint is not documented and the article titles contain Confluence markup which will be a pain to cleanup.

An alternate (and actually documented) endpoint you could hit is here:

This is the URL I used to get the same results (without markup):

With results from a Web Request might show up here:

<li><a href="{{content.iframeSrc}}">{{title}}</a>

Unfortunately the iframe link is lacking any... context. But the data is there.

Oh, here's the fix for that:

<li><a href="{{source.pageId}}">{{title}}</a>

I think this is all the pieces you need. LMK.

Thank you darryl!

With a bit of help from a colleague, we got it working with a bit of automation looking like this:

When an issue is created --> Send web request --> Send email

Web request:
Webhook URL:{{issue.summary.urlencode()}}&limit=3
Header: X-ExperimentalApi - opt-in
Header: Authorization - [my basic auth token]

HTTP method: GET
Wait for response: checked.

To: Reporter
Subject: [Whatever you want]
Content: {{#webhookResponse.body.values}}
<li><a href="{{source.pageId}}">{{title}}</a>

I set "limit=3" in the URL because the UI the end user sees only displays 3 articles, and we want to avoid drowning them with information.
The default limit turned out to be 10.

Thank you Daryl!

I think I managed to delete my first reply, so here it is again :)

With some help from a colleague we got it working.
Our automation looks like this:

Issue created --> Send web request --> Send email.

Web request:


Header: X-ExperimentalApi : opt-in
Header: Authorizatoin : [my basic auth token]

HTTP method: GET

Wait for response: checked


To: Reporter
Subject: [whatever you want it to be]
Content: {{#webhookResponse.body.values}}
<li><a href="{{source.pageId}}">{{title}}</a>

We set the "limit=3" parameter in the URL to match the amount of articles presented in the UI the end user sees.
The default limit turned out to be 10.

Darryl Lee Community Leader Jan 14, 2021

So glad it worked for you.

Shoot, forgot to warn you about the X-ExperimentalApi : opt-in header. That got me when I was testing this.

Good call on limiting it to 3.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events