Static Object allows for custom issue mapping which allows you to define a regular expression pattern that Static Object will use to map commits into issues within your issue tracking software (e.g., Jira). This allows you to see how your tracking estimates compare to the actual time spent by developers in implementing features or fixing bugs.
In order to issue map successfully, your developers will need to include a JIRA issue number in the commit message or title.
Issue mapping can be found on the organization settings page, under Issue Mapping.
You will need to submit a regular expression (regex) and an Issue tracker URL.
Here is an example of a commit by the Static Object development team:
At the front of the title is [S-480]. This is mapped to JIRA using the regex:
The regex is accompanied by an Issue tracker URL such as: https://staticobject.atlassian.net/browse/SO-%d
Next to the commit name is a link to take you to the JIRA that is linked to that commit.
Additional Regex Examples:
matches "Commit on PROJECT-123" and "project-123 commit message"
matches "Message [S123]" and "[so123] Checkin message"
matches "Commit BAB-123" and "D-123 work in progress"
What can issue mapping be used for?
Issue mapping is used to connect the work being done by your developers to the issue/task in your issue tracking software. By mapping issues you can see the impact required for different projects. You can use that data to forecast for future projects or com[are to the actual time spent.
If you're not sure how to create a regular expression, feel free to reach out to our support team firstname.lastname@example.org and we'd be happy to set one up on your behalf.