The Cost Capitalization Report makes it easy to see how much time teams and individuals are spending on capitalizable work, and empowers accounting teams to export the details they need with no effort from engineering.

minware’s patent-pending time model automatically calculates what people are most likely working on using a combination of signals from code and ticket systems. The charts in the report display time spent per Assignee Work Month so accounting teams can simply multiply the capitalizable work months by salary to determine capitalizable costs.

The charts in the Cost Capitalization Dashboard provide you:

• A holistic view of your capitalizable and non-capitalizable work per month
• The capitalizable work ratio breakdown per team and per person
• Capitalizable work time per project, epic, and issue type
• An exportable table of capitalizable work time down to the ticket level

By default, the dashboard assumes tickets in epics are capitalizable, and tickets not in epics are not capitalizable. If your team uses a different signifier for capitalizable work, you can easily configure the capitalization parameter on the dashboard by following these steps:

1. Click on the “Ticket or Epic is Capitalizable” button on the top right of the dashboard to open the minQL editor.
2. Update the minQL formula to specify how your team identifies capitalizable work.

If you have a custom field called "Capitalizable" and the value is "Yes", use this syntax:

ticket.get('level0parent').get('capitalizable') === 'Yes' || 
ticket.get('level1parent').get('capitalizable') === 'Yes'

minQL uses a similar syntax to Javscript. Here, level0parent means either the ticket itself if it is a “story” or “task” type issue in Jira, or its parent if it is a subtask. level1parent means itself if it is an “epic” type issue in Jira, or its parent epic. The === is important because otherwise the whole expression will be false if the level1parent does not exist. Finally, custom field names are converted to lower-case (hence capitalizable), but field values are case-sensitive.

If you use a different signifier for capitalizable, you can find it by referring to the ticket properties in your minQL property reference report, and updating the minQL accordingly. Please reach out to us at support@minware.com and we’ll be happy to help!