We are road-testing Tempo to replace our previous time tracking system completely. There seems to be a couple of gaps
It seems to me that only solution to this is "meta issues" that are never closed. Is there a better solution? Did I miss a feature?
Update: I experimented with "Internal Activities". It looked promising at first, but it only allowed me to plan work, they don't seem to allow me to log time against that activity.
I suggest you use Internal issues in Tempo Timesheets for non-issue activity
Internal issues is intended for logging work against issues that are common to users like vacation and sickness hours.
Please also take a look at the Using Internal issues in Tempo example
Regarding presales activity you may want to evaluate if you can use Tempo Accounts.
The Account Manager gives a way to address different dimensions for done work, other than the JIRA issues themselves.
Hope this helps
Our solution to this, in brief:
Each new Account:
We can then log work against the presales project. For issues on normal projects there is only one Account and this will be selected by default. For issues on the Pre-sales project, the person has to manually select the Account that the issue is associated with when creating the Issue.
We can then report in two ways:
Its a bit odd to me that none of the major agile PM tools offer project level time tracking. Given that most agilists i've met would agrue against tracking actual time spent (aka "effort") on stories/tasks due to the overhead, hassle, and uselessness of it in general, I guess everyone is relying on project/client-level time tracking to be handled by their accounting or payroll system.
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG