Setting Tempo Account Field With JMWE

[Paul Alexander]

With Tempo Timesheets moving to Forge, I have discovered in our new sandbox env that this syntax no longer works. Does anyone have an alternative template that will work? This has worked for seven years. I'm on Atlassian Coud with JMWE.

The error in the JMWE log in our new sandbox env with the latest Tempo bits is simply this.

Error | Template Error | (string) Error: availableOptions filter: only applies to custom fields implemented by apps

For all of my Jira spaces, I have an affiliated Tempo Account that ends in 'Support'. I use this Nunjucks template on a Post Function (Set Issue Fields JMWE app) on a Create workflow step to set the Tempo Account for a given Work Item Type. I hope to keep this employed with the shift to the latest Tempo build soon.

{% set regex = r/Support/ %}
{% for account in "Account" | availableOptions %}
   {% if regex.test(account.value) %}
     {% set proj = account.config.scope.projects2 | find({id:issue.fields.project.id | int}) %}
     {{ account.id if proj and not proj.attributes | find('notSelectable')}}
   {% endif %}
{% endfor %}

Thanks a bunch,

[Arkadiusz Wroblewski]

Hello @Paul Alexander 

I recommend opening a ticket with Appfire/JMWE support. The exact workaround depends heavily on whether JMWE can natively resolve Tempo's new Forge object fields within a "Set Issue Fields" post-function. Since Tempo's transition to Forge, their architecture has moved completely away from the old selectable Account field behavior. They can easily point you on right direction.