Post

3 followers Follow
0
Avatar

Personal Log Entries

Hi, It would be great it it was possible for a PM (or anyone else) to create a personal log of items (reference to Prince 2 PM log entries). Then to enable the option to change these log entries into a Case if necessary.

Kind regards,

Michael

Michael van Haastrecht Not planned

Please sign in to leave a comment.

3 comments

0
Avatar

Hi Michael,

Thank you for sharing your idea! Can you also provide us with a business use case regarding this? 

Tom Do 0 votes
Comment actions Permalink
0
Avatar

Michael,

I think you have an excellent point, the first part of which is relatively simple I think.

To create a personal log, I would create a 'to-do' task called 'project name' PM log and then use the discussion panel within that task to create my date stamped log entries.  Unless I choose to notify anyone then the log is only visible to me.

That said I agree your suggestion would provide a very useful feature.

Phil Smith 0 votes
Comment actions Permalink
0
Avatar

Hi Tom (and Phil),

 

As a PM I get a lot of project related information that I cannot process immediately, Prince 2 refers to this as the PM log or PM diary. At a later stage I can review these and decide on the next step to create a risk, Issue, Request or Task from it. Rather then using a different tool like a spreadsheet or a Word document I would prefer to do this inside Clarizen to have it in the same tool and simplify the process.

At the moment I have implemented this as a simple Issue of the type "Personal Log Entry" and have created a custom action that pops up a window for the information in the projects module and creates the Log entry for me. A separate View in cases lists my Log entries.

Ideally I would like to have a menu option doing this anywhere within Clarizen as you might need this at any point.

At this stage I have kept use of Clarizen for users very simple and at this point do not use To-Do Tasks (as there are some trends for using Agile Team Board for this) nor Discussions.

Michael van Haastrecht 0 votes
Comment actions Permalink