modules/trac/files/order-permissions.csv - Issue 5735669590654976: #753 - set up an order system to let eyeo employees file order requests

Delta Between Two Patch Sets: modules/trac/files/order-permissions.csv

Issue 5735669590654976: #753 - set up an order system to let eyeo employees file order requests (Closed)

Left Patch Set: #753 - set up an order system to let eyeo employees file order requests Created July 22, 2014, 12:47 a.m.

Right Patch Set: #753 - set up an order system to let eyeo employees file order requests Created Aug. 6, 2014, 12:38 p.m.

Left:
Right:

Use n/p to move between diff chunks; N/P to move between comments.

Jump to:

Left: Side by side diff | Download
Right: Side by side diff | Download

LEFT	RIGHT
1 accountants,REPORT_CREATE,TAGS_ADMIN,TICKET_ADMIN,TICKET_INVOICE_RECEIVED,TICKET _MANUAL_PAYMENT_DONE,TICKET_MANUAL_PAYMENT_REQUIRED,TICKET_ORDER_URL,TICKET_PAYM ENT_TYPE,TICKET_TRACKING_URL,TIMELINE_VIEW	1 accountants,REPORT_CREATE,TAGS_ADMIN,TICKET_ADMIN,TICKET_INVOICE_RECEIVED,TICKET _MANUAL_PAYMENT_DONE,TICKET_MANUAL_PAYMENT_REQUIRED,TICKET_ORDER_URL,TICKET_PAYM ENT_TYPE,TICKET_TRACKING_URL,TIMELINE_VIEW,SEARCH_VIEW

2 buyers,REPORT_ADMIN,TAGS_ADMIN,TICKET_ADMIN,TICKET_BATCH_MODIFY,TICKET_MANUAL_PA YMENT_REQUIRED,TICKET_ORDER_URL,TICKET_PAYMENT_TYPE,TICKET_TRACKING_URL,TIMELINE _VIEW	2 buyers,REPORT_ADMIN,TAGS_ADMIN,TICKET_ADMIN,TICKET_BATCH_MODIFY,TICKET_MANUAL_PA YMENT_REQUIRED,TICKET_ORDER_URL,TICKET_PAYMENT_TYPE,TICKET_TRACKING_URL,SEARCH_V IEW

3 staff,TICKET_APPEND,TICKET_CREATE,TICKET_VIEW,TICKET_VIEW_SELF,TIMELINE_VIEW	3 staff,TICKET_APPEND,TICKET_CREATE,TICKET_VIEW,TICKET_VIEW_SELF,SEARCH_VIEW,REPOR T_VIEW,TAGS_VIEW,TICKET_EDIT_CC,TICKET_MODIFY
Wladimir Palant 2014/07/22 13:52:24 SEARCH_VIEW and REPORT_VIEW? SEARCH_VIEW and REPORT_VIEW? mathias 2014/07/24 16:36:49 This entire file has been taken directly from the Show quoted text On 2014/07/22 13:52:24, Wladimir Palant wrote: > SEARCH_VIEW and REPORT_VIEW? This entire file has been taken directly from the attachments in the Trac ticket. I have to discuss your points with Phill, especially because I can only guess the intentions behind the permission assignments in this file.
4 reviewers,REPORT_ADMIN,TAGS_ADMIN,TICKET_ACCEPT,TICKET_ADMIN,TICKET_BATCH_MODIFY ,TICKET_INVOICE_RECEIVED,TICKET_MANUAL_PAYMENT_DONE,TICKET_MANUAL_PAYMENT_REQUIR ED,TICKET_ORDER_URL,TICKET_PAYMENT_TYPE,TICKET_TRACKING_URL,TIMELINE_VIEW	4 reviewers,REPORT_ADMIN,TAGS_ADMIN,TICKET_ACCEPT,TICKET_ADMIN,TICKET_BATCH_MODIFY ,TICKET_INVOICE_RECEIVED,TICKET_MANUAL_PAYMENT_DONE,TICKET_MANUAL_PAYMENT_REQUIR ED,TICKET_ORDER_URL,TICKET_PAYMENT_TYPE,TICKET_TRACKING_URL,SEARCH_VIEW
Wladimir Palant 2014/07/22 13:52:24 No need to repeat TIMELINE_VIEW everywhere, staff No need to repeat TIMELINE_VIEW everywhere, staff group already has that permission. mathias 2014/07/24 16:36:49 See my reply/comment above. Show quoted text On 2014/07/22 13:52:24, Wladimir Palant wrote: > No need to repeat TIMELINE_VIEW everywhere, staff group already has that > permission. See my reply/comment above.
5 trev,admin

6 philll,admin

7 fhd,admin

8 trev,reviewers

9 philll,staff

10 fhd,reviewers

11 till,reviewers

12 christian,buyers

13 nadja,accountants

14 admin,TRAC_ADMIN	5 admin,TRAC_ADMIN
Wladimir Palant 2014/07/22 13:52:24 This is a group, not a user. This is a group, not a user. mathias 2014/07/24 16:36:49 AFAIK Trac does not differ, at least not in case o Show quoted text On 2014/07/22 13:52:24, Wladimir Palant wrote: > This is a group, not a user. AFAIK Trac does not differ, at least not in case of the permissions. Wladimir Palant 2014/07/31 09:46:53 No, it doesn't - but the permissions for the group Show quoted text On 2014/07/24 16:36:49, matze wrote: > AFAIK Trac does not differ, at least not in case of the permissions. No, it doesn't - but the permissions for the groups are defined further above. Anyway, doesn't matter any more with your recent changes.
15 arthur,buyers

16 Testinger,orderstaff
Wladimir Palant 2014/07/22 13:52:24 I think we decided to always assign users to group I think we decided to always assign users to groups in the administration UI, keeping this csv file in sync isn't practicable since reapplying it has issues (it only adds permissions but doesn't remove them). mathias 2014/07/24 16:36:49 Agreed. Yet this is still not optimal, at least no Show quoted text On 2014/07/22 13:52:24, Wladimir Palant wrote: > I think we decided to always assign users to groups in the administration UI, > keeping this csv file in sync isn't practicable since reapplying it has issues > (it only adds permissions but doesn't remove them). Agreed. Yet this is still not optimal, at least not without making the production-data available for testing purposes and defining an alternative (vagrant/puppet) setup mechanism based on that data.
LEFT	RIGHT