2
1
0

We're trying to perform a sync of the Tempo Account custom field but we run into an error :
Unexpected error occurred. Error when attempting to serialize the custom
field `Account` because Exalate does not support it's type

We wrote the rule such as:

issue.customFields."Account".value


Is this sync even possible ? In your Tempo sync documentation, you're only talking about worklogs

  1. user-3fd1a

    Hi Patricia- is this cloud or server?

    Can you also elaborate on the use case?



  2. Patricia

    It's in Jira Server version 8.3.2 and Exalate 4.6.2-j8 


  3. Patricia

    Screenshot of our sync

  4. user-3fd1a

    We'll have to use the tempo  provided Java API's. 

    My day is pretty packed today, can you give it a try - else I will have a look whenever there is a gap.


CommentAdd your comment...

1 answer

  1.  
    1
    0
    -1

    Hi Patricia


    I had some time to dig around the tempo plugin.


    An account has the following properties


    • category:null,
    • customer:null,
    • status:OPEN,
    • global:false,
    • id:1,
    • links:[com.tempoplugin.accounts.link.api.AccountLink@6b047001],
    • customerId:0,
    • key:AN1,
    • billable:false, t
    • empoContact:null,
    • monthlyBudget:null,
    • categoryId:0,
    • name:AN1


    You can use any of these fields and transport them over to the other side with a statement like



    replica.customKeys.accountName = issue.customFields.Account.value?.name
    replica.customKeys.accountKey = issue.customFields.Account.value?.key
    
    




      CommentAdd your comment...