Consider if Franz is a good use case for centralized messages and slack and mail
estimations in tshirt size
time logging per ticket and per project
create ticket page should include more project details and title
explain good practices per field, good project management
export to org mode and pdf of the backlog or a ticket
UI notifications balloon
add tags to tickets and to projects
Emacs package to connect to LucidPlan
add comments (with optional parent-identifier like wikimusic) on a per-ticket basis
Add details about created-at last-edited-at on tickets and projects
Abstract the backlog options mechanics into more general logic
project user permissions
ticket history, any edit operation should be logged
quick actions from list view
icons in select option now supported
milestones
file attachments in tickets and projects
Create web forum and support forum per project, where questions can also be publically viewed
allow to save per-project documentation
allow users to create new tickets, with certain permissions, in certain projects
i18n work and gettext overall
take ideas and inspiration for features from openprokect and jira
implement HATEOAS for lucidplan REST API
progress bar for projects (how many tickets done % but configurable)
comments per ticket
add deadlines feature
REST support /api/v1
Add configurable log destination: stdout, rolling file, etc
ensure lucidplan numeric human id is per project and thus auto increment must be manual
add assignee system for tickets
fix serif to sans serif in google chrome many places
add about and motivation page, truly agile
prioritization of tickets and priority sort
Add different sorting capabilities
use uuidgen from lib, remove syscall
add ticket search functionality in backlog
create single ticket reading mode - detail page
improve done and rejected support in Kanban and backlog
mobile responsiveness
project metadata, description and URL