Comment 6 for bug 528786

mpt you're right that we shouldn't unnecessarily expose internal names.

I do see people occasionally getting confused about this in programs
other than Launchpad, for instance marking bugs in Bazaar that are
affecting the use of bzr by developers of some other project. Many
projects are either tools or things that can be depended upon. (There
is of course a certain background radiation of people randomly
changing things.)

I think to use this aspect of Launchpad, users do need to have a
mental model that they can create a new row in that table of
project/status/importance/milestone. They may not know that they're
called 'tasks' but they do need to know that there is a thing like
this and what it means.

(There is of course the issue that creation is not undoable.)

I think the bug as stated is still true: the two things sound similar
but are totally different. There are various fixes. For instance we
could say "also needs fixing in ...". Deryck has a draft branch that
unifies all the task-creating things into a single link which might
help.

--
Martin <http://launchpad.net/~mbp/>