#1787 Evaluate sfx vs allura ticket permissions

v1.0.0
closed
sf-4 (350)
General
nobody
2015-08-20
2011-03-23
Mark Ramm
No

Determine if the majority of sfx ticket permissions can be transfered over to allura. Perhaps with some tickets going into a general tracker and others going into a private tracker as in allura project (to preserve the privacy of security issues.)

If necessary evaluate the cost of adding a subtractive permission bit for allura to support more of the sfx tracker ticket permissions.

Discussion

  • Mark Ramm - 2011-03-23
    • milestone: limbo --> mar-31
     
  • Dave Brondsema

    Dave Brondsema - 2011-03-24
    • summary: Evaluate sfx vs allura permissions --> Evaluate sfx vs allura ticket permissions
     
  • Dave Brondsema

    Dave Brondsema - 2011-03-24
    • size: --> 4
     
  • Rick Copeland - 2011-04-12
    • status: open --> in-progress
    • assigned_to: Rick Copéland
     
  • Rick Copeland - 2011-04-13
    • SFX allows certain users to be designated as ticket assignees, whereas allura allows tickets to be assigned to anyone in the project
    • SFX allows tickets to be designated as 'private', making them viewable/editable only by the reporter and ticket admins

    To handle migrations, my recommendation is to add full ACLs with ALLOW and DENY to artifacts [#1909]. Keeping private tickets in a private ticket tracker would be sufficient to migrate existing tickets, but would be a step back in functionality, as tickets couldn't be 'private-ized' as they can now. Once full ACLs are implemented, we can mimic the 'private ticket' option by adding a 'private' checkbox which adds the following ACL to the ticket [#1940]:

    • (ALLOW, Admins, *)
    • (ALLOW, reporting user, *)
    • (DENY, , )

    This should be sufficiently close to what a private ticket does now. I'd estimate that once the ACL support is in place, adding a private flag to tickets should be a '2', with the ACL support being a '4'.

     

    Related

    Tickets: #1909
    Tickets: #1940

  • Rick Copeland - 2011-04-13
    • status: in-progress --> closed
     

Log in to post a comment.