The notification received from movement of a story along the Kanban board needs to be more descriptive. For example the body of the email of current notification for stories moved along our Kanban board is as follows:
--------------------------------------------------------- Current email body -----------------

Larry Daniels changed '0012345: User request' (B-03842) on 11/21/2013.
________________________________________
Created By: Larry Daniels
Create Date: 11/21/2013
Related To: 0012345: User request

---------------------------------------------------------- Requested change to email body -----------------
ID:
Title:
Requested by:
Owner:
Previous Status:
Current Status:
Created By: Larry Daniels
Create Date: 11/21/2013
Related To:
------------------------------------------

The fields ID, Title, Requested by are all available in the definition of the story. A field called Status is also available, but it reports the current status of the story, so we need the previous status of the story included in the email body. The other fields (Created By, Create Date, and Related To) are currently reported in the body of the email.

Comments

  • It would be better if the notification email would contain some basic information of the changed story/task (e.g. ID, title, changed by), and all changed fields with the previous and new values.

  • I agree, any fields that were changed - the from and to values should be in the body of the email.

  • I agree with adding more information to the email. We have a group of people who would benefit immensely if they had more information when they receive the email that a new request was added. They are on our front lines answering questions for customers. The email, as it is today, does not give them enough information without accessing VersionOne. Just some additional summarized information would be a big help.