How to set Tempo Account field to null in an automation?

Jonathan Porta March 11, 2025

Hello, 

 

I use a automation to create a Jira ticket from a JSM ticket, how can I ensure that in the newly created ticket, the field Account from Tempo is left empty?

Initially I was not even setting it, but it seems to take the first value available.

Then I tried to copy it from the JSM ticket (where it should be null, as it is not used), same result, first value available.

Then I tried to set it with json:

{ "fields": { "Account": null } }

No error, but same result, first value available.

So how can I prevent this field to be wrongly set???

Thanks in advance.

1 answer

1 accepted

Suggest an answer

Log in or Sign up to answer
0 votes
Answer accepted
Jonathan Porta March 11, 2025

It seems that I was too quick to ask...

I discover that every project has can have a default value for this field (Project settings->Apps->Accounts) and it replace whatever value you try to put in your automation on creation.

Just remove the default value and it is properly set to None

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
ENTERPRISE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events