Issue #SCB1439

Activity report on

  *Enhancement SCB1439 -  AttributeGroup viewing permissions*
 
  Scarab Link: http://www.solitone.org/scarab/issues/id/SCB1439
  Module: Scarab


  Activity generated by  Michael Semb Wever ([email protected])  at 05/07/2008 20:24



  *Comments*
  - By Michael Semb Wever - 05/07/2008 20:24 ---
  "Ok. I'm pushing ahead with this stuff because (a) it's important to me and (b) i'm working in trunk where we are free to roll back changes before any upcoming release if there are still doubts. Infact i'd rather in such a case that we disabled the feature rather than roll it back so that users like me could enable it with something like scarab.scb1439.enable=true in build.properties.

Regarding the remaining points:
>- Needs to be tested the XML Export security (maybe this is not a problem, because it's more an Admin feature????)

It can be considered an Admin feature.

>- Needs to be refactored the code that decides if a given field should be showed to a given user or not.

Can you elaborate please jorge. Is this related to when attributes are dealt with outside of attributeGroups?
I can commit to tackling this before resolving this issue if you feel it's crucial.

>- Emailed activity is a problem when personnel with diverse role sets is assigned to the same issue...

Since email in general is clear text and can easily be snooped then i would suggest to only email the information that was viewable by all personnel attached to the issue. Even email announcing "something unknown has changed", while not ideal, can re-assure people that there's some sort of progress happening. Those people with permissions to see the change can just click on the issue link.

So... with these things in mind ( (a) + (b) + my commitment ) is it ok that i commit the branch to trunk?
  ( i have it merged and updated successfully on my local machine and would quickly like to push it out to sesat.no/scarab/issues but would like to do so through a trunk commit )."