FGdb brainstorm - Revision history

Rfs: /* Needs clarification/discussion */

2008-02-09T00:46:04Z

Needs clarification/discussion

Stillflame: finished moving

2008-02-06T20:44:46Z

finished moving

Show changes

Stillflame: more

2008-02-06T19:12:01Z

Stillflame: more info

2008-02-06T18:57:53Z

more info

Stillflame: different organization

2008-02-06T18:17:04Z

different organization

Shawn at 22:48, 5 February 2008

2008-02-05T22:48:24Z

MichaelWestwind: /* WOULD LIKE TO SEE AVAILABLE */ log/undelete

2008-02-05T20:08:04Z

WOULD LIKE TO SEE AVAILABLE: log/undelete

Stillflame: note about numbers

2008-02-05T19:42:59Z

note about numbers

Rfs at 19:36, 5 February 2008

2008-02-05T19:36:55Z

Stillflame: formatting

2008-01-30T19:29:19Z

formatting

Show changes

@@ Line 119: / Line 119: @@
 * The whole building could be hooked up to the intercom system so people don't have to run around and find others in the warehouse when super busy.
 [[Category: Coders]]
 [[Category: Technocrats]]

@@ Line 38: / Line 38: @@
 * 1 volunteer scheduling should be online, not on paper. this would eliminate double booking, etc.
 * build tasks can't apply towards adoption -- when did that change?
 * there should be a search screen separate from the data entry screen, maybe a tab for each
 * 2 can't access it from the command line (what do they need?  can we add it to the main interface instead?)
 * 4 entering items in a donation need a block of items created so it flows more smoothly.
 * 3 maybe checkboxes for common items donated

@@ Line 22: / Line 22: @@
 * 4 not every terminal should have access to the database and contact information. users should have to sign in (like we used to have to) for certain parts of the database
 * 5 tabbing between fields does not go smoothly when creating donation receipts. sometimes you end up on the wrong field and have to reach for the rodent to get where you want. other times it works fine.
 * 3 gizmo reports should break out disbursements between granted out and adopted out
 * 5 when there are too many items in a sale, it stops displaying the correct total amount and you have to manually calculate the correct amount in order to finish the transaction
 * 3 stuff that gets sold should be organized by where in the building / which department did the work to get it to us, so we can measure how profitable each department is and where our time is well spent. macs, printers, receiving, laptops, build, monitors, basic testing, advanced testing, etc.
 * 4 sometimes the cursor isn't blinking and you don't know where you are and have to click on everything
 * 5 how do you find out if a volunteer adopted a computer and when that happened?
 * 3 front desk should be able to merge contact info between duplicates
@@ Line 38: / Line 33: @@
 * 5 in the disbursements list, when you click on edit it asks if you want to cancel the current disbursement. it says "Do you want to Cancel?" and your options are "OK" or "Cancel". They should be "Yes" or "No".
 * 4 when a volunteer signs up for build or adoption, it should automatically check the volunteer box so you can find them when you're looking for volunteers.
 * 4 thing move around unexpectedly, making it hard to enter data
 * there should be a search screen separate from the data entry screen, maybe a tab for each

@@ Line 3: / Line 3: @@
 Lantz and Martin added numbers which they think are priorities, 1-5 going from least to most important.
-===Basic list===
+==Ticketed or otherwise covered==
 * there aren't enough categories for what people bring in (e.g. All in one printers)
 * the categories don't match the tally form
@@ Line 16: / Line 14: @@
 * when in a receipt (or hours?) can't find people's info (you have to go to contacts to find it)
 * 4 statistics for gizmo statuses report -- you can't specify a whole year. you need to limit it to a few months or less or it times out
 * 4 need easier report generation of things like gizmos given out, gizmos received, hours worked
 * 5 some receipts from the store seemed to disappear last week. i couldn't find the numbers even though i'm sure i didn't delete them
@@ Line 23: / Line 20: @@
 * 2 other startups can't use the sales receipts, since there's no sales tax module
 * 3 there's no debian package -- it's hard to install for startups
 * 3 gizmo reports should break out disbursements between granted out and adopted out
 * 5 when there are too many items in a sale, it stops displaying the correct total amount and you have to manually calculate the correct amount in order to finish the transaction
 * 3 stuff that gets sold should be organized by where in the building / which department did the work to get it to us, so we can measure how profitable each department is and where our time is well spent. macs, printers, receiving, laptops, build, monitors, basic testing, advanced testing, etc.
 * 4 sometimes the cursor isn't blinking and you don't know where you are and have to click on everything
 * build tasks can't apply towards adoption -- when did that change?

@@ Line 69: / Line 69: @@
 ** the drop down should either not be there, or it should have the full list it had before you hit refine, and refine on the fly
 * 4 a way to use the database to create ALL invoices, this would include invoices for recycling
 ==More stuff==
@@ Line 95: / Line 96: @@
 * ? There should be a log for all changes to sales and donations so that deleted or changed entries can be found.  Ideally this would be coupled with an undelete or revert function.
-===shawn's request===
+===Report Requests===
 It would be very, very, incredibly useful if the database could more easily

@@ Line 93: / Line 93: @@
 * 4 Could the “create” and “”cancel” buttons in donations be farther apart. I have been known to click the wrong one and have to start all over again,
 whew!
 ===shawn's request===

← Older revision		Revision as of 19:42, 5 February 2008
Line 1:		Line 1:
	Just because something is on this list doesn't mean it will get fixed, is broken, or even pertains to the FGdb application. But this is the place to put suggestions and beug reports for FGdb. We will organize what we find here and try to match up bugs and feature requests with existing tickets and use this as a factor in setting priorities.		Just because something is on this list doesn't mean it will get fixed, is broken, or even pertains to the FGdb application. But this is the place to put suggestions and beug reports for FGdb. We will organize what we find here and try to match up bugs and feature requests with existing tickets and use this as a factor in setting priorities.
		+
		+	Lantz and Martin added numbers which they think are priorities, 1-5 going from least to most important.

	===Basic list===		===Basic list===