Discussion

What a planner means

Discussion is an activity-specific conversation between a project manager in P6 and team members using P6, P6 Team Member Web, P6 for Android, or P6 for iOS. Oracle: a discussion is an exchange of information, such as a question, answer, or general information that is specific to an activity. The messages to and from team members are saved with the activities and are available to anyone who has access to the project. If more than one team member is assigned to the same activity, all messages are captured in the same dialog box for that activity.

Professional: Activity Details → Discussion tab. Enter a message, Post; it appears in the Comments field. Only users with the Add/Edit Activities Except Relationships privilege can post a comment. You can show all messages, only received, or only sent, and sort newest-to-oldest or oldest-to-newest.

EPPM: Activities → Discussion detail window. Ask questions, respond, and post general information. Discussion Comment displays the message about the activity; anyone with access to the project can view these comments. Name is the user who entered the comment. Post adds your message to the Comments field. If you have the relevant privilege, you can delete comments that are no longer relevant (Context → Delete). Show: All / Sent / Received. Sort: newest to oldest or oldest to newest.

Unread Comments (General column): Oracle: the number of comments posted to the activity since you last reviewed the comments in the Discussion detail window. You can sort and filter on it. It serves as a notification for new comments. Project Managers use it to see how many unread comments are in a given project.

REST: UnreadCommentCount is “the number of Team Member Discussion comments associated with the Activity which have not yet been read.” That is not Feedback / IsNewFeedback.

Team Member Web: view and post messages in the Discussion dialog box; all messages are saved with the selected activity. A number on the Discussion icon is the number of unread messages. You can communicate with the project manager or another team member assigned to the same activity.

This is not Activity Feedback (TASKFDBK / TASKNOTE / rev_fdbk_flag). It is not a notebook (TASKMEMO). It is not an issue (PROJISSU). It is not Timesheet Notes. It is not TASKPRED.comments (relationship Comments). It does not date the activity.

See Activity Feedback, Notebooks (MEMOTYPE / TASKMEMO / WBSMEMO) — Not Schedule Logic, Issues and Thresholds — Not Schedule Logic, Timesheets Are Approved Hours; Apply Actuals Posts Them.

XER

Oracle’s project XER data map lists TASKFDBK (Activity Feedback), TASKNOTE (Activity Notes to Resources), TASKMEMO (Activity Notebook), and TASKPRED (with a comments column labeled Comments). The cited TOC has no Discussion, ActivityComment, or Unread Comments table. TASK has no Unread Comments column. Do not invent a Discussion %T.

REST ActivityComment is an API object, not an XER table. Do not write these as %T / %F columns. Oracle-labeled fields:

Oracle listed AssignmentObjectId, DeleteDate, DeleteUser, IsRejected, LastUpdateDate, LastUpdateUser, and RejectionComments on that page without a published meaning. Do not invent those meanings.

TASKPRED.comments is relationship Comments. TASKFDBK / TASKNOTE are Feedback. TASK.rev_fdbk_flag is New Feedback. None of those is Discussion.

Microsoft Project

Desktop Project has no Discussion thread and no Unread Comments count. It has a single Notes field: comments you enter about a task, resource, or assignment (RTF; Task Information → Notes).

Notes ≠ Discussion. Do not map Discussion comments to MSP Notes and call them the same object. A converter may put one P6 text field into Notes; that is a product choice, not an identity. Do not claim MPXJ can write a real MPP.

Don't

• Treat Discussion comments as TASKFDBK / TASKNOTE / Feedback, as TASKMEMO / a notebook, as an issue, as Timesheet Notes, or as TASKPRED.comments.
• Treat REST UnreadCommentCount as IsNewFeedback / rev_fdbk_flag.
• Invent a Discussion table or Unread Comments column on a project XER parse.
• Write REST ActivityComment field names as XER %T / %F columns.
• Map Discussion to MSP Notes and call them the same object.
• Claim MPXJ writes a real MPP.