Good ideas

• Make a rocking promotional site. This site can then be "changed" into being the wiki for Gjallar.
• Make the feature list page complete. Duh, just do it. :)
• Support for RSS somehow. Typically a Process administrator could decide how and what a Process wants to expose as RSS.
• Support for "public" Processes. Today you can not see anything until you login, and you need an account for that. (Jonas Lindskog at Toolkit is actually itching to take this one)
• Improved Wiki support. There is a swiki formatter, but not much else is tested. Linking conventions, recent changes, search etc. It might boil down to Pier integration.
• Offline operation. The ground work is there but conflict detection and resolution needs to be added - at least in a simple form. And testing.
• Filters and search. This one is a bit complex, lots of stuff is working but the UIs needs work and the query engine a bit too I think.
• Aministration UIs. Categorization of objects, Workflow graph editing, form editing, permissions etc. etc.
• Timeline support. Since all modifications are Transactions we can offer process wide or global History views, and not just per case.
• Interactive graphviz graphs. Graphviz supports generating image maps so we could make stages and transitions "clickable".
• Improved case linking. Linking two cases should be very easy, and currently it is not - it requires to click edit, enter a case number, press an add button, press save.
• Weaving linked cases. When a case has linked cases we could offer weaved views where we interleave the history (or/and notes) of all involved cases.
• Weaving history and notes. The threaded notes view could optionally be made to include all the other events that the History view shows.
• Documentation . End user documentation and programmer documentation.
• Documentation generation. Using a wiki syntax for documenting Gjallar (this Swiki) itself and defined Processes (using the integrated help) could be extended to be able to generate polished printed documentation by generating Lout/LaTeX or similar. The Wiki syntax would then be the "single source format" used.
• SCM integration. Not sure how or what - but some might want it.
• Graphs and statistics. Some kind of neat statistics included in Gjallar not needing export.
• ODBC mirroring. The ability to mirror reports out using ODBC instead of generating reports as files.
• Defining SOAP API. Defining a selected SOAP API in order to create and update cases using SOAP etc.
• General scavenging. Simply look through what other issue trackers can do - Mantis, JIRA etc and pick any good ideas. ;)
• Color coding. Make some neat color coding scheme that can be driven by different fields of the cases, like age, stage etc.
• More concrete Txns for model manipulation. Today we liberally use "modify definition" Txns etc, which should be minimized.
• Permission based navigation panel. Somehow map permissions onto entries in the panel thus being able to hide/show different parts depending on user.
• Better separation of permissions and the ui. (not sure what this means, Balázs knows more).
• Ajaxian UI. Utilize more Ajax functionality available in Seaside. For example, the help today is manually "hacked" and could probably be easier done using Seaside/Scriptaculous (showing/hiding).
• Visually show when a case can not move. Colors? A different status?
• Might be nice to see criteria on fields even when they are met.
• Ability to easily add persons on the fly (name, email etc). The idea was to add this as an option to a certain field type for persons.
• Export/import of persons using vCard. There is a library at SqueakSource we should use.
• Scaling of Graphviz graphs. Sometimes they are simply too large.
• Enabling other visual features of Graphviz. Graphviz has tons of features we could expose.
• Testing write barrier in Magma or performance.
• Parse and "remove" email signatures in description and notes. Match exact and then move up to name, turn into tooltip using Scriptaculous thus folding it away
• Add script hook for email popping. For more advanced tricks.
• Fix the problem of loosing edits in forms due to navigation. This can probably be solved using Ajax or something...
• Releases/milestones. The idea to be able to group issues in relation to important points in time, for planning. Needs analysis and possibly input from how others systems deal with this.