Edit: Sorry, I've just realized that I haven't really contributed a lot to this on HN. Specifically - how does the ticketing system work? What is the difference between a ticket and an issue? It seems that you can have a ticket that has many issues, but issues can have many tickets...
Does an issue encapsulate a lot of tickets? If so, is the primary work done on the ticket or the issue? The reason I ask is how do you allocate the unit of work to specific people.... or is this not the point of the app?
Sorry in advance for the huge number of questions.
An issue has a one to many relationship with tickets. I built it, as I found I'd get many tickets about the same thing from different users. I wanted to be able to focus on solving the macro issue and not manage many issues. Terry Smith is one of the thinkers behind it.
has_many :issue
and in issue.rb, it has the line: has_many :ticket
Why a M:N mapping of issues to tickets? Were you planning of future expansion?any thoughts ?
That said, it is lacking so many critical features any business of significant size would need to take it seriously, and to be honest, the market is glutted with good options of all costs and capabilities so I'm curious to know what your intention was in creating this?
That being said, I see the value of tagging. Perhaps a future addition.
Haven't seen this before…
www.ticketdesk.co alex@ticketdesk.co 123456
I've disabled much of the cron / emailing.