Broken custom field "account" made by Tempo

[Volodymyr Kryzhanivskyi]

My problem is that probably after migration from a Jira Cloud installation, Account custom field id (10002) remained from there, but Tempo created the one with different id (11001) in Server installation.

In logs I see this:

 /rest/tempo-accounts/1/config/customfield [c.t.a.customfield.impl.AccountsCustomFieldServiceImpl] Could not find account custom field with Id: 10002

My Account field have another id. I cannot even guess how this problem can be solved. Thank you for any help.

[Clarissa Gauterio]

Hi Volodymyr,

We had the same issue a few days ago and we fixed by changing the Account field from Cloud to be used on server:

update customfield
   set cfkey='NULL',
       customfieldtypekey='com.tempoplugin.tempo-accounts:accounts.customfield',
       customfieldsearcherkey ='com.tempoplugin.tempo-accounts:accounts.searcher'
 where id = 10002;

And we also deleted the unused Account custom field from the server:

delete from customfield where id = 11001;

After performing the above changes, we restarted Jira and our tempo Account issues were fixed.

Cheers,

Clarissa

Atlassian Consultant, Blended Perspectives 

[Jan Dewald]

Thank you so much for sharing! This developed into a major problem for us - no more reports, no association of accounts with logs, all gadgets not working (except one).. etc. Kind regards ++ all the best!

[Clarissa Gauterio]

Glad to know that helped!

[Jan Dewald]

Problem was fixed today - and voilá - it´s great to see everything in its place after such a long time!