Tempo: How can I manage multiple account WBS codes across a single issue?

[michael.trappitt]

Currently the organisation uses tempo time recording to write to issues with account WBS loaded to then extract at the end of the month and write hours to SAP. At present account WBS codes are changed each quarter to meet finance requirements but this necessitates a clone and close of any outstanding tickets with time written to them.

In testing for closed off periods changing the WBS on an issue will then change it for all records, is there a way to avoid this without cloning and creating a new issue key for the records requiring a WBS update?

[Susanne Götz _Tempo_ · Accepted solution]

Hi @michael.trappitt ,

In Tempo, it is possible to link more than one Account to a project. 

When an Account is set on the issue (in the Account custom field), this Account will be connected to all worklogs on the issue. Changing the Account will cause all worklogs to be connected to the new Account set in the custom field.

To avoid this problem, you can use Account as work attribute (https://tempo-io.atlassian.net/wiki/spaces/THC/pages/293766657/Using+Accounts+as+Work+Attribute+and+Linking+it+to+Worklogs+-+Tempo+Server).
When using a work attribute, an additional field is added to the Log Time dialog. This gives the option to select any Account that is linked to the project and the worklog information does not change when the Account in the custom field is updated.

You can then create a new Account each quarter, link this new Account to the project and close/ archive the old Account.

Best regards
Susanne
Tempo team

[Eduardo Anflor - MindPro]

Have you tried this app? https://marketplace.atlassian.com/apps/1221714/contractspro-contract-manager-for-jira?hosting=server&tab=overview

It has an alternative way to handle multiple accounts into contracts and track their progress.