•  
     
    story #10063 homogenize service administration
Summary
Empty
homogenize service administration
Empty

For Service Level permissions:

  • Have the same UI & pattern (to be slightly reworked)
  • Leverage "new service permissions" widget (already in use in git, mediawiki, frs and svn plugin)

For services:

  • Docman: update the UI and use the new select box
  • Wiki:
    • Extract old permission inherited from legacy matrix (as done in story #9281 for FRS)
    • + merge with already existing wiki permission for read & write
  • Tracker v5: introduce service level admin permission
  • News & forums: Extract old permission inherited from legacy matrix (as done in story #9281 for FRS)
  • Continuous integration: Introduce service level admin & access permissions
  • Agile dashboard & Trafficlights: introduce service level admin permissions
    • This admin permission is limited to groups that are already tracker v5 admins
  • Instant messaging, Mailing lists, SVN Core, Tracker v3, CVS: nothing done
Empty
Empty
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
#10063
Manuel Vacelet (vaceletm)
2018-07-17 11:22
2017-03-09 11:30
4552

References
Referencing story #10063
Referenced by story #10063

Follow-ups

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
  • Status changed from Ready (stalled) to Canceled
  • Category set to