We are running some large projects that need to be broken down into parts for accounting purposes. For example, we have one project which includes the development of four training courses. Each course needs to have its labour costs tracked separately. But because there is significant overlap between the courses, it is inconvenient to put each into a separate project.
In addition we are working on integrating Jira with Quickbooks by exporting the tracked time through the Jira API.
The solution we have come up with temporarily is using Epics. We assign issues to Epics and have developed our own custom reports we run on our database to determine how much time was tracked to issues in specific Epics. But there are a few problems with this:
1 - It is difficult to assign an issue to an Epic after it has been closed
2 - Tempo has no concept of Epics, nor does the Jira API, so it is difficult to build a tool to export hours into Quickbooks.
I am looking at using Versions instead of Epics because they appear more native to Jira, are accessible through Agile boards and appear to have some representation in Tempo as well. It feels like that would be abusing the Versions feature though.
Has anybody faced the same problem? How do you deal with breaking projects down in parts for labour hours accounting when necessary?
