Update an Iteration

[michaelkleinhenz]

Description

As a user, I can update an iteration for a space and change title and start and end dates.

Functional Acceptance Criteria

1. The user can select an iteration from a list of all iterations of the current space. The list order is undefined for this story.
2. The user can update an iteration from a dialog that opens when an iteration is selected from the list.
3. The user can change the title (alphanumeric value), the start date (date) and the end date (date).
4. It is not possible to update an iteration with an empty title.

Non-functional Acceptance Criteria

1. The "list/update iteration" view is easily accessible from anywhere in the system UI.

Dependencies

1. Userstory Create Iteration for a Space #409
2. Userstory Close an Iteration #411
3. Userstory Set/Update Iteration on Work Items #412

[qodfathr]

Logic tied to the current date is generally not worth the effort. I should be able to set the start date to a date preceding today. Let's say I forgot to create an iteration for this month -- why are you having the system deny me creating it? A warning that I can turn off may be okay, but this shouldn't be a hard-coded rule. [e.g. QuickBooks warns me when I make accounting entries which are more than 6 months old -- just to be sure I didn't type the year wrong. But it does let me put these entries into the system.]

[michaelkleinhenz]

@qodfathr ok, updated the story.

[ldimaggi]

Will there be a history/audit trail for updates made to the start/end dates?

[Mgranfie]

Would this be part of the larger log/audit file?... I am not sure if this
would be something the user would want to see as part of the experience?...

On Mon, Oct 31, 2016 at 2:41 PM, Len DiMaggio notifications@github.com
wrote:

Will there be a history/audit trail for updates made to the start/end
dates?

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

[qodfathr]

While I'm in favor of auditing almost everything, auditing changes to iteration dates strikes me as something that almost no one would care about. (Yes, I can come up with some use cases. But I believe they very rarely happen.) If we can capture this data, let's do so, but let's not work on any UX around it until we've got more data on usage (how often does it happen) and need (someone wants to review the data).

[Mgranfie]

+1 on not auditing the Iteration dates right now.

On Wed, Nov 2, 2016 at 8:58 AM, Todd Mancini notifications@github.com
wrote:

While I'm in favor of auditing almost everything, auditing changes to
iteration dates strikes me as something that almost no one would care
about. (Yes, I can come up with some use cases. But I believe they very
rarely happen.) If we can capture this data, let's do so, but let's not
work on any UX around it until we've got more data on usage (how often does
it happen) and need (someone wants to review the data).

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

[michaelkleinhenz]

@Mgranfie @qodfathr yes, not part here, because this has a much bigger scope. Logging/auditing is an epic of its own. There were talks in Westford about being able to roll the system back to any point in time, etc..this is much bigger than what can be done in this story.

[qodfathr]

@michaelkleinhenz right, a 'true, 100% rollback' would need something like this. Maybe a 'mostly true, 99% rollback' will suffice. :) Thanks for the reminder on this subtlety.

[michaelkleinhenz]

Important addition: we might need some way to select or view an iteration from a list of iterations. How are they ordered in that list? What iterations are displayed there? This is needed in the story.

[Mgranfie]

Michael,

In the current designs we have a list of iterations, right now they are
listed by date, start date being the identifier.

Let me know if this makes sense.

Thanks,
Monica

On Tue, Nov 8, 2016 at 8:41 AM, Michael Kleinhenz notifications@github.com
wrote:

Important addition: we might need some way to select or view an iteration
from a list of iterations. How are they ordered in that list? What
iterations are displayed there? This is needed in the story.

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

[maxandersen]

Since date are optionals sorting by date does not make sense IMO.

It should be an ordered sequenced list.

[Mgranfie]

Proposing to go for alphabetical, until and even if we have dates...

On Tue, Nov 8, 2016 at 8:52 AM, Max Rydahl Andersen <
notifications@github.com> wrote:

Since date are optionals sorting by date does not make sense IMO.

It should be an ordered sequenced list.

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

[michaelkleinhenz]

As alphabetical would only be a temporary solution until we defined something better, can't we just go for "unsorted" for now? Thats what we've done on the worklist..just leaving out any sorting and display the items as they are in the data(base).

[qodfathr]

Iterations are ordered. It is a list of data (actually, it's hierarchical -- remember, iteration is a path data type) -- and lists are, by definition, ordered (otherwise we'd call them a bag).

So if I type in

Iteration 1
Iteration B
Iteration III

then that's the order of the iterations. This is super-critical for the UX to have any degree of sanity.

As a lower priority feature, I should be able to drag/drop reorder and reparent them.

e.g.

Release 1
  Sprint 1
  Sprint 2
Release 2
  Sprint X
  Sprint Y

I should be able to drag Sprint X to somewhere else, such as:

Release 1
  Sprint 1
  Sprint 2
  Sprint X
Release 2
  Sprint Y

or even

Release 1
  Sprint 1
    Sprint X
  Sprint 2
Release 2
  Sprint Y

[Mgranfie]

Todd,

Based on your examples, are we limiting the names of the Iterations and
Sprints to "Iteration #", "Sprint #" and "Release #" then?

This as a requirement. These are auto generated with a numeric appendage?

Thanks,
Monica

On Wed, Nov 9, 2016 at 11:15 AM, Todd Mancini notifications@github.com
wrote:

Iterations are ordered. It is a list of data (actually, it's
hierarchical -- remember, iteration is a path data type) -- and lists are,
by definition, ordered (otherwise we'd call them a bag).

So if I type in

Iteration 1
Iteration B
Iteration III

then that's the order of the iterations. This is super-critical for the UX
to have any degree of sanity.

As a lower priority feature, I should be able to drag/drop reorder and
reparent them.

e.g.

Release 1
Sprint 1
Sprint 2
Release 2
Sprint X
Sprint Y

I should be able to drag Sprint X to somewhere else, such as:

Release 1
Sprint 1
Sprint 2
Sprint X
Release 2
Sprint Y

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

[qodfathr]

@Mgranfie No, they can have any name you want. No autogeneration of any kind. (Although we should consider some auto generation for the future. Often I will want "Sprint n, Sprint n+1, Sprint n+2..." auto generated for some value of n, likely also with dates (e.g., "every two weeks starting with jan 12, 2017").

But that's not for today. We can discuss in January.

The initial development methodology selection should be able to prepopulate the project with a list of initial recommended iterations. (e.g., the Scrum methodology might give you "Sprint 1," "Sprint 2," ... "Sprint 6" as a reasonable start. The user can then modify or delete these, of course.)

[Essjaysee]

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

[michaelkleinhenz]

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