Blueprint assignments for “CoOrg”
This listing shows the assignment of work for blueprints currently associated with CoOrg. The drafter is responsible for getting the specification correctly written up and approved. The approver is usually the person who would sign off on the specification.
1 → 7 of 7 specifications | First • Previous • Next • Last |
Priority | Name | Definition | Delivery | Assignee | Drafter | Approver |
---|---|---|---|---|---|---|
1 Undefined | The configuration API should be reworked | 0 Approved | 8 Beta Available | Nathan | Nathan | Nathan |
1 Undefined | Integrate CoOrg with OpenID | 0 Approved | 0 Unknown | Nathan | ||
1 Undefined | A data directory should be available | 0 Approved | 5 Started | Nathan | Nathan | Nathan |
1 Undefined | Installation of new languages should be possible from the admin | 0 Approved | 5 Started | Nathan | Nathan | |
1 Undefined | The admin should have the possibilty to change meta tags | 5 New | 0 Unknown | Nathan | Nathan | |
1 Undefined | Plugins should be enabled/disabled | 5 New | 0 Unknown | Nathan | Nathan | |
1 Undefined | The update manager should get an improvement | 5 New | 0 Unknown | Nathan | Nathan |
1 → 7 of 7 specifications | First • Previous • Next • Last |