Just an idea.

The price and billable fields are not shown on the node views. A good idea, as users may not want to show these fields to customers are employees who can view them.
for example, users might want to allow project managers or assigned people or author etc... to add/edit them but not be allowed to set/change/see these values (using defaults instead).

I suggest, on all Storm node types, grouping these fields together and creating permissions to allow view/edit (maybe separate permissions) on these fields.

I know this would add to the already long list of permissions (which I think it's good to have lots them).

What do people think?

Comments

juliangb’s picture

juliangb commented

It might be worth looking at CCK field permissions, and what happens to that with Fields in Core in D7.

If that is ported as I suspect it will be / has, then it would probably be a better use of time for us to work on the port to D7 or simplifications in D6 which will aid that process.

juliangb’s picture

juliangb commented
Status: Active » Closed (won't fix)

This will be fixed by #1915320: Move to a Field API based approach.

Once this is done, using a module such as Field Permissions should do the trick.