Alpina - September 6th Goals

[maxandersen]

As a user I should be able to by Sept. 6th 2016 (Alpina):

CLI

• Login to get Token (Lets use CentOS Linux 7 #118)
• Create a WorkItemType (CR REST Endpoints, DB Backend) (Rename models.NewRepository to models.NewWorkItemRepository #119)
  Create Work Item Type (extension) #121
  • Create work item type name Epic with some fields:
    • $ ./bin/alm-cli --host demo.api.almighty.io create workitemtype --payload '{"extendedTypeName":null,"fields":{"system.owner":{"Type":{"Kind":"user"},"Required":true},"system.state":{"Type":{"Kind":"string"},"Required":false}},"name":"Epic"}'
  • Read (Show the work item type named system.issue):
    • $ ./bin/alm-cli --host demo.api.almighty.io show workitemtype --name "system.issue"
  • Fields (Basic understanding of Field types, String, State, User) (Lets use CentOS Linux 7 #118/Rename models.NewRepository to models.NewWorkItemRepository #119) Add WorkItemType Field type verification/tests #77
    • ID
    • Title
    • Description
    • State
    • Assignee
  • Transitions (Basic understanding of state transition) (Rename models.NewRepository to models.NewWorkItemRepository #119)
    • Open / Closed
• Update a WorkItemType (Stretch Goal) (Rename models.NewRepository to models.NewWorkItemRepository #119)
• List WorkItemTypes (Rename models.NewRepository to models.NewWorkItemRepository #119)
  • $ ./bin/alm-cli --host demo.api.almighty.io list workitemtype
• Execute a query from CLI to import issues from remote issue tracker Create model for 'other' issue tracker integration #24
  • Data to fetch:
    • Title
    • Description (including convertion of Remote text flavor(makrdown/jira wiki))
    • Status (including mapping from Remote status to ALM Planner status)
    • Add link (maybe just as text) back to remote issue.
  • Issues will be added to list of workitems (WorkItem Mapping : Move original ( pulled from remote ) items from Tracker table to WorkItems #170)
• Remote Provider integration for GitHub (priority 1) Create GitHub Remote Issue Provider integration #102
• Remote Provider integration for Jira (priority 1) Create Jira Remote Issue Provider integration #103
• Remote Provider integration for Trello (Stretch goal) Create Trello Remote Issue Provider integration #104
• Remote Provider integration for Bugzilla (Stretch goal) Create Bugzilla Remote Issue Provider integration #105
• View a list of workitems (Lets use CentOS Linux 7 #118) As a User I should be able to List created WorkItems #101
• Create a WorkItem (Fix #55 - Debugging instructions for the command line using delve #117) As a dev I should be able to CRUD a WorkItem via CLI #22
• View WorkItem (Fix #55 - Debugging instructions for the command line using delve #117/Lets use CentOS Linux 7 #118) As a dev I should be able to CRUD a WorkItem via CLI #22
• Update a WorkItem (Lets use CentOS Linux 7 #118) As a dev I should be able to CRUD a WorkItem via CLI #22
• Transition a WorkItem from Open to Done (Rename models.NewRepository to models.NewWorkItemRepository #119)

UI

• Login via GitHub (Lets use CentOS Linux 7 #118) As a user I should be able to log on via central Auth provider #20 As a Team member I should have access to a Project #19 As a user I should be able to be part of a Team #17 As a User I should be able to have different permissions #16 As a user I should be able to login into the application. fabric8-ui/fabric8-planner#8
• View a list of workitems (Lets use CentOS Linux 7 #118) As a user I want to see work items in a list view fabric8-ui/fabric8-planner#2
• Create a WorkItem (Fix #55 - Debugging instructions for the command line using delve #117) As a user I want to be able to create a new work item. fabric8-ui/fabric8-planner#3
• Create a WorkItem Based on the CLI created WorkItemTypes (Stretch Goal) (Rename models.NewRepository to models.NewWorkItemRepository #119)
• 3 ‘predefined’ types of WorkItems (To be used by the Team) (Lets use CentOS Linux 7 #118/Rename models.NewRepository to models.NewWorkItemRepository #119) As a user I want to be able to use a predefined work item type. fabric8-ui/fabric8-planner#6
  • UserStory
  • Feature
  • Bug
• View WorkItem (Fix #55 - Debugging instructions for the command line using delve #117/Lets use CentOS Linux 7 #118) As a user I want to be able to view the details of a work item. fabric8-ui/fabric8-planner#4
• Update a WorkItem (Lets use CentOS Linux 7 #118) As a user I want to be able to update / edit a work item. fabric8-ui/fabric8-planner#5
• Transition a WorkItem from Open to Done (Rename models.NewRepository to models.NewWorkItemRepository #119) As a user I want to be able to transition a work item from open to done. fabric8-ui/fabric8-planner#7

Local test usage (#118)

• https://trello.com/c/yiijOl7q/65-create-app-distro-interested-users-dev-can-build-run

[tsmaeder]

This slipped by me when we did the planning: "Update a work item type" seems much more like a stretch goal for Sep. 6 than "List work item type". It involve both conceptual work and I would guess quite a bit of implementation

[aslakknutsen]

@tsmaeder Yeah, agree. 'Update' has a lot of 'baggage' as to what that actually means. It's not just a DB update. Let's swap them.

[AdamJ]

@maxandersen Can we somehow add information to this list about whether a design has been finalized or not before development starts on an item? Just want to keep it as streamlined as possible :-)

[maxandersen]

@mindreeper2420 What is on this card ends Tuesday - lets figure out how to do this for next sprint - starts on Wednesday. ok?

[AdamJ]

@maxandersen works for me. Thanks.

[maxandersen]

We finished this sprint, result is at demo.almighty.io.