----- Forwarded message from Jesse firstname.lastname@example.org -----Date: Mon, 10 Apr 2000 13:43:36 -0400
From: Jesse email@example.com
To: Tobias Brox firstname.lastname@example.org
Subject: Re: Web plans
So … a web user would typically start with some login stuff that isn’t
done yet, continue with either the buildquery page or a bookmark/startpage
or something pointing to a pre-made query. Then comes the listing. Both
the search and the listing needs some work, but it can be demonstrated.
The ticket is selected, and the user ends up in Ticket/Display.html…this
page clearly needs a lot of work (I hope I can manage to get back to work
after dinner), so I can see more on it. What are your plans … should it
be more or less like the display we use here today, with possibility for
changing the attributes at top,
Actually, probably with static attributes and a link to “Modify this ticket” “Update this ticket” , etc. Note that Modify and Update are different.
Update is an enhanced comment/respond that will become the “default” way
to do things like resolve, set status, etc. the basic idea is that people should
be encouraged to write notes on every update.
and then links to Update (with the
transaction message quoted) at each transaction?
Sounds about right.
+47 22 925 871
----- End forwarded message -----
jesse reed vincent – email@example.com – firstname.lastname@example.org
pgp keyprint: 50 41 9C 03 D0 BC BC C8 2C B9 77 26 6F E1 EB 91
"It’s buried in the desert, got sand in it, melts Nazis. You know,
the Ark of the Covenant" – siva