Set/Update Iteration on Work Items

[michaelkleinhenz]

Description

As a user, I want to add and remove work items to an/from an iteration by setting the iteration for a work item.

Functional Acceptance Criteria

1. The user can set the iteration of a work item on the work item detail view. Changes to the iteration are stored on clicking the save button, not in-place.
2. The user can set the iteration from the work item list. Changes are saved in-place.
3. The user can select the iteration from a list of open iterations for the current space.

Non-functional Acceptance Criteria

None.

Dependencies

1. Userstory Create Iteration for a Space #409
2. Userstory Update an Iteration #410
3. Userstory Close an Iteration #411

[Mgranfie]

@michaelkleinhenz a user should also be able to directly interact with a work item, in the list, to associate it with an iteration.

[nimishamukherjee]

@michaelkleinhenz - Are we looking at iterations only from a work item perspective?
The other scenario would be open an iteration and add multiple work items.

[michaelkleinhenz]

@nimishamukherjee currently only from the work item perspective.

[michaelkleinhenz]

@Mgranfie updated the story. I am curious how the UX will look for that :-)

[Mgranfie]

Hi All,

SJ is working on the UI for this, so looping her in to the discussions...

On Fri, Oct 28, 2016 at 3:37 AM, Michael Kleinhenz <notifications@github.com

wrote:

@Mgranfie https://github.com/Mgranfie updated the story. I am curious
how the UX will look for that :-)

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#412 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ARTwqwQcQS0D_f0D4_1XR7y3vq_rjUlBks5q4aYxgaJpZM4KiheC
.

[ldimaggi]

I think we will want both:

• In the work item view, associate the workitem with an iteration.
• In an iteration view, assign 1..N workitems to the iteration.

[Essjaysee]

@michaelkleinhenz On # 3 "select the iteration from a list of open iterations for the current project", do you mean that you're on the project page and indicating which iterations are associated with the project?

[michaelkleinhenz]

@Essjaysee no, it means that on either the WI detail view or on the WI list view, the user can select the iteration to be set on the WI from a list of all available iterations. The list of available iterations is scoped to the current project (as every project has an own list of iterations).

Welcome to the Team :-)

[VineetReynolds]

I have a question, based on some thinking I was doing for the acceptance criteria. Here are a couple of scenarios:

Given a project PizzaTheHut,
And the project has 3 WIs - a story (first WI) with a UX subtask (2nd) and Coding subtask (3rd),
When the story is assigned to an iteration (sprint X)
Then the subtasks should also be assigned to the iteration.

Given a project PizzaTheHut,
And the project has 3 WIs - a story (first WI) with a UX subtask (2nd) and Coding subtask (3rd),
When the UX subtask is assigned to an iteration (sprint X)
And the coding subtask is assigned to an iteration (sprint X+1)
Then the story would be completed only in sprint X+1.

Would we cover these scenarios as part of this sprint? WIs with relationships may not be that easy to handle in iteration planning, depending on the nature of the WILT.

[Essjaysee]

@michaelkleinhenz Thanks for your reply, makes sense!

[Essjaysee]

@joshuawilson @aslakknutsen @maxandersen @michaelkleinhenz Wireframes for iterations: https://redhat.invisionapp.com/share/KA9CAYL7M

[michaelkleinhenz]

This issue was moved to fabric8-ui/fabric8-planner#648