| No.
|
Text
|
What?
|
Who?
|
When?
|
| 1
|
Patches:
- Source-Code has patches. These are then needed, when we also change object classes, update or modify data.
- Check the optimal solution to roll out these patches between CWI and TMU
- Question: How shall we handle necessary roll-backs (for example if data modifications went wrong).
|
To Do
|
MEI
|
2013-10-23
|
| 2
|
Modularisation:
- Separate Modules into Web and Service
|
Info
|
All
|
2013-10-18
|
| 3
|
Release Management
- Is ok, but the difference between stable and unstable must be explained better (Major can be unstable too? No).
|
Info
|
All
|
2013-10-18
|
| 4
|
API
- Requires more information about the minimum amount of need calls and what is expected.
- First step is the API for stoney core
- Second step is the API for stoney backup (on-line backup)
- Third step ist the API for stoney mail
- RestfullYii or on GitHub: RestfullYii makes a good impression on CWI.
- Communication between JavaScript (Client) and Yii-Framework (Server) need some thoughts from CWI.
|
Info
|
All
|
2013-10-18
|
| 5
|
Testing
- Will be done as described under Testing.
|
Info
|
All
|
2013-10-18
|
| 6
|
Super User
Reseller Person (can only belong to one reseller, but to multiple customers and can be employee of the reseller and the customers)
-
sstBelongsToResellerUID: 1234567
Customer Person (can only belong to one reseller but to multiple customers and can be employee of these customers)
-
sstBelongsToCustomerUID: 1234567
|
Info
|
All
|
2013-10-18
|
| 7
|
Person
- Three separate forms
- Super User (can add new Resellers, Modules, make People to Reseller People)
- Reseller (
|
Info
|
All
|
2013-10-18
|
| 8
|
Suche
- The results need more information, depending on the level you have logged in. For example
- Provider: Needs the information to which reseller and which customer the person belongs to.
- Reseller: Needs the information to which reseller customer the person belongs to.
- Customer: Knows, the person belongs to the customer.
|
Info
|
All
|
2013-10-18
|
| 9
|
Default views after login:
- Provider Person: Product overview page of the provider, where they can also change the settings and defaults of a service/product (global activate/deactivate modules).
- Reseller Person: Product overview page of the reseller, where they can also change the settings and defaults of a service/product (activate/deactivate modules for themselves and therefore for their customers).
- Customer Person: Product overview page of their own services/products.
These views need to be defined.
|
To Do.
|
TEI/MEI
|
2013-10-25
|
| 10
|
PDF Creation
- Will ODT work with current offer?
- A possibility would be to exchange PDF creation with the screen redesign.
|
Info
|
All
|
2013-10-18
|
| 11
|
Roles and rights
|
Info
|
All
|
2013-10-18
|
| 12
|
Next steps
- Prioritise the next functionality
- Create Mockups and documentation, including LDIFs
- Create Enhancements in the issue tracker and add to desired version
- Ask for quotation
- Clarify any questions and update Enhancements/Documentation
|
To Do
|
MEI/CWI
|
2013-10-18
|
| 13
|
Split current selfcare into
|
To Do
|
MEI/CWI
|
2013-10-18
|
| 14
|
REST API
|
Info
|
CWI
|
2013-10-18
|
| 15
|
Different Forms for different users
|
Info
|
CWI
|
2013-10-18
|
| 16
|
Line length (table field) restriction via CSS
|
Info
|
CWI
|
2013-10-18
|
| 17
|
VM-Manager
- Change Reseller and Customer by adding Person
|
Info
|
CWI
|
2013-10-18
|
| 18
|
Priorities
- Core
- VM
- Mail
- Backup Customer View
|
Info
|
All
|
2013-10-18
|
| 19
|
Lizenz Abklärungen
|
Info
|
All
|
2013-10-18
|
There are no 