How to define columns of a smart-card rendered filter-table through Automation?

[Walter Lamm]

Hey there,

when pasting a url to a JQL-search into an issue desription it automatically gets rendered into a cool smart-card with predefined columns like so:

Before I stumbled upon this feature I had Automation automatically insert a lookup list of specific issues and some of their fields into a table in the description field when my rule was triggered. Problem was that this list was static. If there were any issues added, the list wouldn't get updated.

With this feature I could include a live view of a JQL-search but I have one problem:

The columns seem to be predefined and I need different ones and another order of these.

So my question is this: Is it somehow possible to define these columns in Automation?

When I change them in the description manually the change gets logged in the card's history but there are no apparent changes I could use to format my insert:

Thanks a lot!

[Bill Sheboy]

Hi @Walter Lamm 

I hypothesize the answer is: "no, that is not possible."

Many of the macros for the Description field cannot be added (or updated) directly with automation rule edits to the field.  It appears there is more data the macro uses that is not visible to the rule actions.  This may be demonstrated if you write the Description to the audit log (or call the REST API functions), and the selected columns for the issue list macro are not included.

I spent quite a bit of time on this a couple of years ago trying to add / edit some macros and was not successful.

Kind regards,
Bill

[Walter Lamm]

@Bill Sheboy Okay, thanks for confirming my assumption.

That's a shame and not really understandable why anyone would implement such cool macros that oviously can manually be customized and not give us the option to use these customizations in Automation. 

On top of not being able to edit the columns I've found out it's not even possible to insert the table itself. If I use [smart-card] as pictured in my second screenshot above it gets rendered as a smart-card and not as a smart-table. Am I missing something? Why are two different renders of a JQL-search named the same? 

[Bill Sheboy]

Sorry, I do not have answers for that.

There is little documentation on the markdown features regarding field macros: https://jira.atlassian.com/secure/WikiRendererHelpAction.jspa?section=all

My hypothesis is many Jira features have no REST API functions to access the data which configures the feature, and so automation rules cannot access them.  There is an Atlassian Document Format (ADF) for advanced formatting, although I could not find specifics on using that macro with a rule.

You appear to be the site admin for a paid Jira license, and so I suggest submitting a ticket to Atlassian Support to ask if it is possible: https://support.atlassian.com/contact/#/

When you hear back from them, please post what you learn to benefit the community.  Thanks!

[Walter Lamm]

I've asked Atlassian Support but nothing new to report unfortunately.

Thanks for your time nonetheless.

[Thomas Tegeler]

Hi, i know it's a bit late, but if somebody else needs this. You can do this via Webhook and also edit the columns:

PUT https://your-domain.atlassian.net/rest/api/3/issue/ISSUE-KEY

{
"fields": {
"description": {
"type": "doc",
"version": 1,
"content": [
{
"type": "blockCard",
"attrs": {
"url": "URL",
"datasource": {
"id": "IDK-HONESTLY",
"parameters": {
"jql": "YOUR-JQL",
"cloudId": "CLOUD-ID"
},
"views": [
{
"type": "table",
"properties": {
"columns": [
{ "key": "issuetype" },
{ "key": "key" },
{ "key": "summary" },
{ "key": "assignee" },
{ "key": "priority" },
{ "key": "status" },
{ "key": "updated" }
]
}
}
]
}
}
}
]
}
}
}


I got the Datasource "id" when i made a GET Request on an Issue with such a table. For me it is always the same id no matter which Content is in the table, so i suppose to make a GET Request yourself and use this one for every new table you add to the issues.

I hope i could help.