Question about Tempo Account Custom Field and Payload to bulk update it

[Hugo Navia]

I'm currently running a migration test and I need to update the Account value for around 670 thousand issues.

I've written a python script that works although I haven't been able to solve the rate-limit at the moment. So I decided to try a Bulk Update approach but, the payload seems to have the wrong format.

Here's the information of the field in Cloud and the payload I'm sending.

Thank you in advance for any hints.

Field JSON:

{ "id": "customfield_10506", "key": "io.tempo.jira__account", "name": "Account", "untranslatedName": "Account", "custom": true, "orderable": true, "navigable": true, "searchable": true, "clauseNames": [ "Account", "cf[10506]" ], "schema": { "type": "option2", "custom": "com.atlassian.plugins.atlassian-connect-plugin:io.tempo.jira__account", "customId": 10506 } },


payload = {

    "selectedActions": [f"customfield_{JIRA_ACCOUNT_FIELD_NUMBER}"],
    "selectedIssueIdsOrKeys": issue_keys,  # Make sure issue_keys is not empty
    "editedFieldsInput": {
        "singleSelectFields": [
            {
                "fieldId": f"customfield_{JIRA_ACCOUNT_FIELD_NUMBER}",
                "option": {
                    "optionId": tempo_account_id
                }
            }
        ]
    }
}

[Valerie Knapp · Accepted solution]

Hi @Hugo Navia , thanks for your post. 

Tempo has a Slack channel for developers and partners. Please contact them, using a ticket, and they can help you with this https://marketplace.atlassian.com/apps/6572/timesheets-by-tempo-jira-time-tracking?hosting=cloud&tab=support .

Best wishes