Is Each Task Name In Your Projects Unique?

[Doug_Den_Hoed__AtAppStore]

Hi folks,

We've just released a new version of our Enterprise Stopwatch solution that now (optionally) will show (and search) each Task's parent Tasks, for context. In doing so, we are aware (thanks to user feedback) that for some patterns of work, it is common practice to configure Tasks in repeating phases, as follows and as per the screenshot below:

Out of curiosity, I'm interested to learn how common this practice is, so would appreciate your insight: is each Task name In your Projects unique, why, and does it cause any drawbacks?

Regards,

Doug

Session 1

    Plan

    Do

    Review

Session 2

    Plan

    Do

    Review

Session 3

    Plan

    Do

    Review

cc: note to self @Doug_Den_Hoed__AtAppStore 

[KathyHa]

For the clients I work with, we often do have a structure as outlined in your example - so task names are not unique.

[CalvinFold]

Uniqueness is encouraged for task names, as it is less confusing for Workers on their timesheets as well as reports that report back on tasks.

But…I suspect it doesn't happen 100% of the time. We do hear about it now and again.

We've mostly solved this with doing multiple iterations, uniquely named, on our templates. It encourages preferred behavior.