Suggestion: "Add lock" feature to date-values

[Tony G]

From GH #4:

To avoid erroneous modification (manually or with "Offset Task Dates"), dates should have a "lock feature / read-only-tag".

[Kore Engineer]

Is it possible reconsiderate this suggestion?  It's easy do mistakes

[.dan.g.]

Hi KE

>> It's easy do mistakes

Can you describe exactly what type of mistakes you are talking about pls?

[Kore Engineer]

Two types of mistakes: First do modifications in the wrong task. In a normal day this not happen frecuently but when I do general reorganization in the document ( with a lot of cut/paste and changes in dates and allocated) and the document have 200 tasks it is easy do mistakes. Second in gantt view, in this view it's easy change dates unintentionally. I use the software in project management. The core task (foundations, walls, equipment erection, electrical installations) have to be preserved from any mistake but aditionally I have-want to manage my day-to-day-tasks (call a contractor to ask a technical question, for example) in a very dinamic way. Both type of tasks core&day together is perfect but isrisky too. If I can lock core-tasks I will work much more relaxed. Now I have a ice skate feeling :)

Enclose picture of the concept

[.dan.g.]

Thx KE.

Firstly let me say that I think this would be a valuable feature so my questions are simply a way of exploring the idea.

From the picture its looks as though the lock feature would affect all task attributes, not just dates. Is that what you are proposing?

[Kore Engineer]

Yes, lock all task attributes and very import avoid remove the task by mistake, in my case this type of elimination-error is (relatively) frecuent and critical.

You're questions are welcome!   

[.dan.g.]

Then I agree (for 7.2)!

[.dan.g.]

Should a lock on a task also affect its subtasks?

On Tuesday, 28 February 2017 17:31:00 UTC+11, Kore Engineer wrote:

[Kore Engineer]

On Wednesday, March 1, 2017 at 12:28:07 AM UTC+1, .dan.g. wrote:

Should a lock on a task also affect its subtasks?

Myself no. A example of use could be:

task: CONCRETE FOUNDATION TANK 03 Alloc to: HORMIGONES PEREZ Start: 02/03/2017 06:30 Due: 03/03/2017 18:30  Core task, locked, in this task is where I writte the comments. This task have to be preserved for proyecto historical records and have values in custom task attributtes, type "$ invoiced", etc. Of course the task that have to be carrefully managed.

subtask: CALL PETER REMEMBER USE CONCRETE TYPE 04 Day-to-day task. High dinamic management. Having made the subtask normally I delete it, or if relevant write a note in parent task to register they realization. If by error delete or modify some date is not funny but is not a disaster.

[.dan.g.]

>> locked, in this task is where I write the comments.

Locking a task will also lock its comments...

[.dan.g.]

A little teaser for you...

Enjoy!

On Sunday, 26 February 2017 20:52:40 UTC+11, Kore Engineer wrote:

[Kore Engineer]

:)

[.dan.g.]

1. Should the lock affect the ability to move the task, either to a new position or to a new parent?

2. Should the lock affect the ability to add/delete subtasks?

On Tuesday, 28 February 2017 17:31:00 UTC+11, Kore Engineer wrote:

[Kore Engineer]

On Monday, March 20, 2017 at 7:14:42 AM UTC+1, .dan.g. wrote:

1. Should the lock affect the ability to move the task, either to a new position or to a new parent? Yes

2. Should the lock affect the ability to add/delete subtasks? No

[.dan.g.]

Hi KE

Check out the preview of 7.2 for task locking.

On Sunday, 26 February 2017 20:52:40 UTC+11, Kore Engineer wrote: