I was asked to add some ticket features so I thought I would put some here.
An extensive revision system to track what all has happened to the ticket. A complete view on the history of a ticket is really needed to make sure people can be pinged and held accountable for the life cycle of a ticket and what information is in it and where it came from.
A linking system so that you can have a document and link tickets to that doc, like a doc describing features and requirements and tickets that are there to implement those features. This maybe a bit out of scope depending on if the design docs are in the ticket system too. The main observation is that having to update a document to point to the tickets that are made supporting that doc manually will never be up to date.
I was asked to add some ticket features so I thought I would put some here.
An extensive revision system to track what all has happened to the ticket. A complete view on the history of a ticket is really needed to make sure people can be pinged and held accountable for the life cycle of a ticket and what information is in it and where it came from.
A linking system so that you can have a document and link tickets to that doc, like a doc describing features and requirements and tickets that are there to implement those features. This maybe a bit out of scope depending on if the design docs are in the ticket system too. The main observation is that having to update a document to point to the tickets that are made supporting that doc manually will never be up to date.