Tickets :: Comment on [#4400] Attach checklist to tickets

* Your Email Address
* Spam protection	Enter the letters below: .__..__ .___.___. . \| \|[ __[__ [__ \|\ \| \|__\|[_./\| [___\| \\|
Comment	>> This kind of thing should _definitely_ be a custom attribute. :) > > > > Our use of Whups would benefit from checklists in two ways: > > > > 1. Granular tickets. Our enhancement-type tickets are granular > enough to speak about in conceptual terms, but when we turn these > tickets over to junior developers to implement, we find they miss > certain details that our architecture/senior developers would know to > do. Having a checklist would allow them to check off those parts of > the ticket they've accomplished and see their progress at a glance. > A workaround is to put one task in one comment, then have the > developer reply to each comment when complete. This works, but isn't > ideal. > > > > 2. Task tickets. We use whups as a client portal as well as for bug > tracking, so we have a "task" type ticket, which refers to an (often > billable) action such as making a production system upgrade. The > client often inputs these tasks, so a checklist helps the client see > -- at a glance -- that each sub-task has been handled. > > > > Attributes do not seem amenable to these use cases:
Attachment
Watch this ticket