While Use Automation to edit link formatting on Paragraph Fields outlines how to create URLs to add to paragraph fields which allow smart URLs to be displayed as smart-link, smart-card or smart-embed, there doesn't appear to be a way to create a URL which will result in a Jira JQL link displaying the List view. Does such a solution exist?
Currently the only work-around I've found is to go the issue after the paragraph field has been updated, click on the smart card and change the display from card to list.
Hi @Michael Dawson -- Welcome to the Atlassian Community!
What do you mean by the "List view"?
Kind regards,
Bill
Hi Bill,
I am referring to the Smart Link list view as described on Smart Link list view , specifically having Jira automation add the URL (which is a Jira search query) to the description field of a Jira ticket and have it display the results as a list view.
The list view is the one you get when you click on this button
And then shows the list with these headers
I have tried constructing the URL using the various options like [URL|URL|smart-card] and [URL|URL|smart-embed], but none of those will default the view to that list view.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that information, Michael.
I have not tried to add those with a rule, and I believe they are macros which create the list from the selection criteria (e.g., URL, search results, etc.). Many of the macros cannot be directly added by a rule's edit action. One way to check is to view the configuration for the macro in the page content using the REST API to view it, and then try to create a new one...again with the REST API as described earlier.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks Bill. I was successfully able to get the view I wanted by using the REST API in the Jira Automation rule to write the description field and populate the URL to display as a list view. That solution isn't ideal, but it is working.
Thanks for your help and suggestion to use the REST API!
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.