•  
     
    story #12975 restrict permission to artifact that are assigned to Contributors
Summary
tracker admin
restrict permission to artifact that are assigned to Contributors

As a follow-up of story #12974 I can go further and ensure that people that are not yet assigned to the artifacts don't see them at all.

In this setup:

  • Triage individual that are "assigned to triage" tickets will have access to all artifacts
  • "Change" individual that are "assigned to change" tickets  will only have access to artifacts that requires them to be involved.

Overview

This new permission cannot fit in current Tracker level permissions as it's strongly coupled with a semantic (contributor) whereas the interface is only oriented toward group management.

The new permission should be handled outside the table "group / permission type" in a dedicated section after:

"Permissions based on semantics"

There would be 1 toggle (on/off) "Contributors have access to artifacts they are assigned to"

When active, as soon as someone is selected in one of the fields selected as Contributor semantic (see story #12974), they will have access to the artifact.

Limits

  • The toggle cannot be enabled if there is no "contributor" semantic set
  • It's not possible to remove completely "Contributor" semantic is the toggle is active

Technical impact

  • The page is updated to Burning Parrot look'n feel to benefit of toggles
  • This is a new code path that need to be added where access to artifact is checked
  • The configuration must be imported with XML export/import
  • The configuration must be inherited at tracker duplication during project creation
  • There is no impact on REST API as tracker permissions configuration are not yet exported in GET /trackers/:id
Empty
Geoffroy Grelot (ggrelot)
Status
Empty
Canceled
Development
  • [ ] Does it involves User Interface? 
  • [ ] Are there any mockups?
  • [ ] Are permissions checked?
  • [ ] Does it need Javascript development?
  • [ ] Does it need a forge upgrade bucket?
  • [ ] Does it need to execute things in system events?
  • [ ] Does it impact project creation (templates)?
  • [ ] Is it exploratory?
Empty
Details
#12975
Manuel Vacelet (vaceletm)
2019-04-08 11:34
2019-02-07 11:37
4057

References
Referencing story #12975
Referenced by story #12975

Follow-ups

User avatar

Initial proposal didn't meet expectations, see parent epic.


  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Status changed from Ready (stalled) to Canceled
  • Category set to
User avatar
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
User avatar
  • So that
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes
  • Acceptance criteria
    Something went wrong, the follow up content couldn't be loaded
    Only formatting have been changed, you should switch to markup to see the changes