Capability types need to be persistently stored
Registered by
Travis Tripp
Capability types need to be persistently stored
Blueprint information
- Status:
- Complete
- Approver:
- Travis Tripp
- Priority:
- High
- Drafter:
- Travis Tripp
- Direction:
- Needs approval
- Assignee:
- Wayne
- Definition:
- Drafting
- Series goal:
- Accepted for trunk
- Implementation:
-
Implemented
- Milestone target:
-
poc-juno-summit
- Started by
- Travis Tripp
- Completed by
- Travis Tripp
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Check in for bp/capability-
Gerrit topic: https:/
Addressed by: https:/
Added REST api for captype derived properties
Addressed by: https:/
bp/
Addressed by: https:/
Testing dependecy branch.
Addressed by: https:/
Testing interbranch dependency
(?)
