Dr. Edward M. Hanna

My feedback

  1. 2 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Microsoft Project  ·  Flag idea as inappropriate…  ·  Admin →
    Dr. Edward M. Hanna shared this idea  · 
  2. 2 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Microsoft Project  ·  Flag idea as inappropriate…  ·  Admin →
    Dr. Edward M. Hanna shared this idea  · 
  3. 12 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Microsoft Project  ·  Flag idea as inappropriate…  ·  Admin →
    Dr. Edward M. Hanna commented  · 

    Agree--this appears to be a BUG! I too have been surprised that the Link to Document icon does NOT appear in the PWA Indicators column--when a link to a document is created. O365 Support has been no help on this issue--appears to be too specialized for them.

    Dr. Edward M. Hanna supported this idea  · 
  4. 256 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    21 comments  ·  Microsoft Project  ·  Flag idea as inappropriate…  ·  Admin →
    Dr. Edward M. Hanna supported this idea  · 
  5. 30 votes
    Sign in
    (thinking…)
    Sign in with: facebook google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  Microsoft Project  ·  Flag idea as inappropriate…  ·  Admin →
    Dr. Edward M. Hanna supported this idea  · 
    Dr. Edward M. Hanna commented  · 

    Tom,

    A very good suggestion. I would say that "accidental constraints" (i.e. those created when you enter a Start date or a Finish date) is an insidious problem with many, many client project schedules that I review. This, of course, leads to a great deal of user frustration when an accumulation of constraints is causing bizarre behavior in their schedules. They frequently blame the product (spreading the news to colleagues) and--when frustration reaches a limit--they stop using the product.

    I would, however, like to suggest an even broader feature (i.e. configurable read-only fields) so that ANY field could be configured to be "read only". In addition to Start and Finish, there are other fields (e.g. WBS) that could benefit from being protected from spurious changes.

    To explain my WBS comment, we don't want the WBS assigned to a task to inadvertently change when it has been mapped to the Project Cost Accounting System using that WBS code. (To be more precise, the OOB WBS code has a renumbering feature--making it unusable for PCAS linkage. So, I would be using an Outline Code as "WBS" and wanting to make that field "read only".)

Feedback and Knowledge Base