Skip to main content

Issue Structure

We use the word issue to describe a standard for a documented piece of work on one of our projects.

Statuses​

An issue's status can be thought of the work state that the issue is currently in.

  • Draft: Default status for when an issue is created, these are considered works in progress.
  • Created: Ready to be brought into a planning session and discussed.
  • Ready For Work: Has been discussed and can be worked on by a contributor for the current or upcoming sprint.
  • In Progress: Indicates that the issue is being actively worked on.
  • Blocked: Signifies work cannot be completed due to another issue or unforeseen circumstance.
  • Pending Review: Work is complete and is awaiting peer review.
  • In Review: The completed work is currently being peer reviewed.
  • Ready For Release: Work has been peer reviewed, signed off on, and is ready to be released.
  • Complete: The work is currently in production and the issue can be archived.

Pointing​

We assign user stories a point value based upon an agreed upon arbitrary standard. A good rule of thumb to use is that the higher the point value on an issue, the higher difficulty/longer time to complete.

Pointing is done using a modified Fibonacci scale, ignoring 0 and having a maximum value of 13.

1, 2, 3, 5, 8, 13
info

It is import to keep in mind that point values are truly arbitrary, and should not be used as empirical evidence for critical planning. They are there for estimations and to give tangibility for something difficult to quantify.

Versioning​

Each completed issue will cause its respected project version to bump (increase) in value upon release. You can view our versioning conventions on our Structures & Conventions page.