Use developer activity data from Swarmia to generate capitalization reports and blend with cost data.
This feature is only available for admin users.
First time setup
This feature is in self-serve alpha. Please contact us via hello@swarmia.com or the in-app chat if you have any questions regarding capitalization or the feature.
Software capitalization reporting is powered by an accompanying investment breakdown. As part of setting up this feature, you'll need to configure your categorization.
A typical way of doing this is via a Jira custom field that's connected to capitalizable initiatives or epics.
- Setup an investment breakdown to capture work that can be capitalized
- Configure Software Capitalization settings
Building reports
- Navigate to Swarmia to export your software capitalization reporting data
- Copy the reporting template from the same view
- Import the Swarmia data to the reporting template (see instructions on the README)
- Optional: blend in cost information for more accurate cost reporting
Frequently asked questions
Q: Can I mark multiple investment categories within an investment breakdown as capitalizable?
A: No, you can only select one category within a breakdown to be capitalizable. That's visible under the software capitalization settings page in Swarmia.
Q: Can I manually categorize work into my capitalizable investment category?
A: It's not possible right now but the support is going to be added to Swarmia.
Q: Can the work be aggregated by a different Jira issue type in the software capitalization report?
A: It's not possible right now but we're going to add support for this in the future. Currently the work is aggregated by the highest level parent that we can find from your Jira issue hierarchy. However, you're able to see the FTE values for any of your issues from Swarmia's UI already.
Q: What's the optional additional issue context field in software capitalization settings?
A: the "Additional context" is an extra column in the work export for providing more context about the capitalizable project (e.g. the reason for capitalization, the capitalization date).
Concretely, it's a field in your Jira issues, e.g. a label or a custom field, that's pulled to the capitalizable work export as a separate column. It can be used for custom reporting purposes if you don't prefer to use software capitalization reporting template.
Q: Can I convert the software capitalization reporting template to a .xlsx file?
A: It's not possible right now as some of the formulas used in the Google Sheet reporting template are not available on Microsoft Excel. We're planning to build a reporting template for Excel in the future.