andrewblake1
commented
10 years ago Maybe. There are issues with this. With a few seconds of thought, I would say, what if you take something away and then put it back?
Technically has been removed. We re added, actually is just making up to what it originally was however we be under the new user as opposed to sys admin. Easy to say just add back as system admin but again not simple code wise
Suggest low priority feature request as opposed to bug. Not as clear cut as would appear I suspect and not holding up the use of the system.
On 11/07/2014, at 5:25 pm, hawea notifications@github.com wrote:
Hi Andrew,
We would like a way to be able to identify materials and assemblies which are added +New to a task. This is because it is hard to tell when checking a list, what was part of the original build from the task template and what are additional special items that have been added afterwards by the planner.
My thought was to add a column or potentially colour code the new items. Could be based on the fact that systemadmin user id = 1. Materials and Assemblies created under other user ids could indicated a new material or assembly.
— Reply to this email directly or view it on GitHub.
Hi Andrew,
We would like a way to be able to identify materials and assemblies which are added +New to a task. This is because it is hard to tell when checking a list, what was part of the original build from the task template and what are additional special items that have been added afterwards by the planner.
My thought was to add a column or potentially colour code the new items. Could be based on the fact that systemadmin user id = 1. Materials and Assemblies created under other user ids could indicated a new material or assembly.