Jira thoughts

The idea here is to reduce the number of ticket templates we have to maintain. The plan is something like

Epics - Project level tickets

Bugs - Something went wrong

Feature - Feature level tickets

Task - A catch-all for anything not covered in other tickets

Subtasks - for breaking down features, bugs and tasks should we need to

Support - support tickets

Projects are defined as short-lived feature driven backlogs. You would expect the features to be large enough to warrant their own project. They should comprise one or more epics with ten or more tasks that may be broken down into many subtasks. Once the feature described by the project is complete, these should be exported to the systems shares and deleted.

Product backlogs are defined as long-running maintenance and improvement backlogs. Small features, bugs and general maintenance tickets would live here.

Operational backlogs are defined as more general purpose backlogs for activities that are not specific to a single product, but might have cross over with one or many products.

Support backlogs are attached to helpdesks and are holding places for contact from users. Tickets here may be dealt with in place or funnelled off to other backlogs

It has been suggested that it might be best to start all new Jira projects, migrating new tickets over and removing the old. This means we could clearly identify tickets that have been reviewed, and we can remove all the old tickets in case they contain PID. Below is what I am thinking