On Sat, May 30, 2009 at 9:26 AM, Darryl L. Pierce <mcpierce(a)gmail.com> wrote:
Added a new migration that creates the mapping table for joining
epics
to their messages.
Added a business rule, Epic.can_comment?. It only returns true if the
given user has a role in one of the products owned by the epic's
project. To support this a new business rule, Project.is_member?, was
added that returns whether a user is a member of project's product
teams.
When an epic is shown, an empty comment is created but not saved if the
user is allowed to post comments. On the epic detail page a comment form
is shown.
Added a new route, comment_epic_path, for posting comments. Added the
supporting action, EpicsController.comment, to receive and process the
comment.
Signed-off-by: Darryl L. Pierce <mcpierce(a)gmail.com>
---
Pushed.
--
Darryl L. Pierce <mcpierce(a)gmail.com>
Visit the Infobahn Offramp: <
http://mcpierce.multiply.com>
"Bury me next to my wife. Nothing too fancy..." - Ulysses S. Grant