Issue Prioritization

OpenStudio uses github issues to track bugs and feature requests. Properly labeling github issues helps everyone understand which issues are most important. Please use the following labels to classify OpenStudio issues in github.

Severity

All bugs should be assigned a severity describing the impact of a bug to the end user. The key here is impartiality and objectivity in judging the bug’s severity. Remember that all bugs seem urgent when you first hear about them. However, personal preferences are not a criteria for giving a bug a severity!

• Blocker - total loss of functionality, file corruption, or crashes
• Major - major loss of functionality, no workarounds
• Normal - some loss of functionality under specific circumstances, may or may not have a workaround
• Minor - minor loss of functionality, easy workaround is present

Feature Request

A feature request is used to label all issues related to missing features. A missing feature which impedes a workflow is a feature request and not a bug report. If a feature was supposedly delivered but does not work properly then that is a bug report.

Component

The component or components that this issue impacts (e.g. SketchUp plug-in, OS App, Measures, etc)

In Progress

Apply this label when an issue has been scheduled for work in Pivotal.

Resolution

If the issue is closed but not fixed, label the final resolution (e.g. duplicate, won't fix, etc) and provide a note explaining the rationale

EnergyPlus Issue

If the issue relates to a bug or missing feature in EnergyPlus then apply this label, link to the EnergyPlus issue if it exists.

Low Frequency

If an issue is known to impact only a small number of users then apply the Low Frequency label.