I think it's a great idea. I'm not sure if this would work, but if it appeared on github, we could use it as an example app that new Lifters could study. Like what we hoped PocketChange would be, but we have more of a need for a ticket system, than a budget app.
On Oct 24, 10:21 am, Marius <marius.dan...@gmail.com> wrote: > I'd LOVE TO SEE a ticketing system built in lift even though there are > so many other solutions out there. > > The things that I'd like to see are: > > 1. When opening a Ticket I'd like to see fields like: > - Summary > - Description > - Severity > - Priority > - Assign to > - Followers. Submitter would add himself/herself as a follower > - Tester > - area/module > - ability to upload content logs, screenshots etc > - ability to specify code snippets that will then be rendered with > syntax highlight. Also links specified in free text to be rendered as > real links. > - Found in version & build > - Seen on branch > > 2. A commiter can: > > - Specify Internal and external dependencies. Such as a defect > depends on a known Scala compiler ticket. > - Mark the ticket as fixed, unreproducible, not a bug, 3-rd party, > deferred etc. and other statuses that can be managed by an admin. > - Ask more questions etc. > - Upload content > - Change priority and even severity ? > - Close a defect ... usually QA closes the defect so in this case > the persons in the Terster section would be able to close it ... > - Build & version when the fix will appear > > 3. General > > - Query defects by owner, severity, priority etc. > - Ability for users to create queries and save those queries. > - Stats & charts about the defect, fix rate etc. Would be nice to > put a link to this stats when we do a release. > - Separate feature requests than actual defects ... to have a visual > distinction. > - Admin site. > - Email notifications. > > This I guess would be a minimum from my perspective. > > Br's, > Marius > > On Oct 24, 4:56 pm, Derek Chen-Becker <dchenbec...@gmail.com> wrote: > > > Hi, > > I feel like I need to take a break from working *on* Lift for a little > > while, but I'd like to do something with my time that would still benefit > > Lift. Since we had a recent discussion on ticketing systems, and we had > > talked a long time ago about dogfooding a ticket system, I thought that this > > might make a good project to work on. I like the simplicity of the GitHub > > issue tracking, but I think it's missing some important things: > > > 1. Email notifications > > 2. Duplicate tracking > > 3. Release planning fields like milestones, etc > > > I do like the integration with Git commit hashes and other intelligent > > hyperlinking in the comment space, but I'm on the fence as to whether I like > > using tags as a generic tool for things like ownership and component > > classification. I could probably be persuaded either way. In any case, does > > this seem like a good project, and if so, do people have requirements, > > suggestions, comments, etc. on the functionality that should be in it? > > > Thanks, > > > Derek > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Lift" group. To post to this group, send email to liftweb@googlegroups.com To unsubscribe from this group, send email to liftweb+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/liftweb?hl=en -~----------~----~----~----~------~----~------~--~---
