|
Issue 0079 in split format
- Summary
- The issue list is hard to use
; Owner: Tim
; Reporter: Tim
; Status: open
; Priority: high
; Version: 1.4
; Subsystem: wiki
; Tags: network, wiki
|
; Summary: The issue list is hard to use
; Owner: Tim
; Reporter: Tim
; Status: open
; Priority: high
; Version: 1.4
; Subsystem: wiki
; Tags: network, wiki
|
|
= Description =
There are several deficiencies in the Fuego issues list, which make it
uncomfortable or inconvenient to use:
* it is slow. It takes a second or two to load every page
* the index page takes about 2.7 seconds to load
* It is hard to figure out how to query the issues
* there is no 'assigned' field (but there aren't really people to assign things to)
* tbwiki doesn't support concurrent operations, so there's the possibility of data corruption
* the form is raw text, and people can mess up the values for fields that should be enumerated types
* more specifically, we're not using enumerated types for some fields that should have them - (tbwiki has some support for this, but we're not using it)
* it is possible to use tbwiki to filter the issues, but it is very awkward, and there is no form to do it.
* there's no way to keep a log of comments on an issue
|
With enough problems, it becomes very unpleasant to use the issues list. It should be
helping keep track of issues that need to be resolved, but it is not.
|
With enough problems, it becomes very unpleasant to use the issues list. It should be
helping keep track of issues that need to be resolved, but it is not.
|
|
= Notes =
Maybe we need to switch to Jira or gitlab for Fuego. It seems like these would solve
our problem (but at the cost of having to administer those systems).
|
Some possible speed problems could be solved by using fastcgi or wscgi.
|
Some possible speed problems could be solved by using fastcgi or wscgi.
|
- backlink
Fuego Issues List
|
; backlink: [[Fuego Issues List]]
|
|
|