Tickets at Improving Works live in one of three (plus one) states:

New

New tickets are exactly that...new. Tickets from paying customers are given the highest priority. Other tickets will sit in this state for a while. If the ticket is a duplicate, or we can't reproduce it, we may mark it as invalid (probably with a comment explaining why). If more information or clarification is required, we might ask for more comments. When we're ready to take on more work, the ticket will then move to...

Accepted

This means the ticket has been included in a Minimum Marketable Feature and approved for addition to the product. At this point, it moves into our development backlog and will be implemented and released at the next available opportunity. When a ticket moves into the development backlog as an MMF, it may be combined with other tickets, enhanced, or changed (to be truly Minimum and Marketable). After that, it gets...

Released

Each MMF in our development backlog is released as soon as it is implemented. We'll update the ticket to let you know it's finished. For details on new releases of Infinitest for Eclipse, check the Release Notes or subscribe to the RSS feed.

Invalid

We may mark your ticket invalid if:

  • we can't reproduce it
  • it's a duplicate of another ticket
  • the problem is addressed in the user guide
  • it's not a problem with Infinitest

Of course, there are other reasons why we might mark a ticket invalid. These are just some examples.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

Continuous Test Runner for Java

Shared Ticket Bins

Pages