Context
our jira instance uses "Initiatives" (the hierarchy ticket-> epic -> initiative come from Jira portfolio)
custom scriptrunner scripts tie account (and its status) to initiative (and its status)
Usecase:
Monday Mar 30 2020, Jira admin changes status of initiative ET-170801 from "inactive" to "active"
...immediately Script makes corresponding account 44019 active . (initiative is tied to account key 44019. )
On Tues Mar 31, "Joe User" files timesheet for previous week on logs time for Friday Mar 27 to ticket NT-10101 (which rolls up to ET-170801 and is tied to account 44019)
Desired Result
=============
Tempo UI blocks Joe User from logging time on Mar 27 to NT-10101. "Account was not active at this date"
Actual Result
=============
Tempo UI allowsJoe User to log time on Mar 27 to NT-10101. "Account was not active at this date"
Guest
| Tempo Products | Tempo Timesheets |
| Tempo Platform | On-Premise |
From one of our finance folk:
A resource [i.e. person] that books cap eligible time to a project prior to the project’s actual start date is a direct SOX deficiency because that has a potential downstream impact to P&L reporting, which gets reported out to shareholders
more details:
specifications are in Section 302 of the Sarbanes-Oxley Act of 2002 (the "Act").
In addition we comply with GAAP rules as well:
RELEVANT ACCOUNTING GUIDANCE
U.S. Generally Accepted Accounting Principles (GAAP) Guidance:
Accounting Standards Codification (ASC) 350-40 Intangibles - Goodwill and Other - Internal-Use Software (ASC
350-40)
ASC 350-50 Intangibles - Goodwill and Other - Website Development Costs (ASC 350-50)
ASC 360-10 Property, Plant and Equipment - Overall (ASC 360-10)
ASC 835-20 Capitalization of Interest (ASC 835-20)
ASC 985-20 Software - Costs of Software to be Sold, Leased, or Marketed (ASC 985-20)
Hi William,
Unfortunately we do not support time based account statuses today. We use other mechanisms, such as the scheduler, to close time logging on a period basis.
We are looking into the feasibility of supporting this, but I would be interested to know what specific regulation you need to be in compliance with. This will help us evaluate the business case for an improvement like this.
Thanks,
Hlynur Johnsen
hi kristin,
we have this setting correct, i.e. this is unchecked:
'user can log time for closed and archived accounts'
the bug in tempo is as follows:
- tempo does not check the 'worklog date' against the "date the account was opened"
Hi William and thanks for the feedback. There is a configuration to prevent users from logging on Closed and Archived Accounts. Can you verify you setting. See documentation: https://tempo-io.atlassian.net/wiki/spaces/THC/pages/292978789/Configuring+Logging+Time+Options+-+Tempo+Server