Im creating automations to work around the issue of not being able to export asset field information. One is working and the other is not. I believe my problem is that the asset field has a space in it. When I try to use {{customfield_11901."Pod Name"}} in automation, nothing gets input into my custom field.
In that same group of assets, I have one automation that uses {{issue.customfield_11664.name}} and that works just fine.
Hi Bill: Did you try taking the double quotes off? I work mostly in Data Center and sometimes that works.
Also what are you trying to export to? In my instance I have Xporter to export but I also have ability to export to word. I just create a template with the Asset place holder and use that to export the data.
Hey Carla!
I have tried taking of the quotes. Also tried an underscore, tried a dash, tried nothing. No matter what, the attribute field won't get moved over to my custom field.
What we're doing is creating a filter in jira, then exporting it to google sheets using Jira cloud for sheets. The thing is, when I export either to CSV or sheets, it shows [field not found] or something to that effect. The workaround provided by atlassian is to export that field to a text field using automation, then export that.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bill, let me check my cloud instance.
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.