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)
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)
Tempo UI blocks Joe User from logging time on Mar 27 to NT-10101. "Account was not active at this date"
Tempo UI allowsJoe User to log time on Mar 27 to NT-10101. "Account was not active at this date"
|Tempo Products||Tempo Timesheets|