Add more options and ending dates to the "Iteration" drop down options

RESOLVED FIXED

Status

()

RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: shell, Assigned: glob)

Tracking

Production
x86
Mac OS X

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
Marco and I discussed adding additional iteration drop downs and also adding the last day of those iterations.

Can we add additional options to the Iteration drop down and add dates to one existing one?
- change existing "37.3" to "37.3- 1/13"
- add "38.1- 1/27", "38.2- 2/10", "38.3- 2/24"
(In reply to sescalante from comment #0)
> Marco and I discussed adding additional iteration drop downs and also adding
> the last day of those iterations.
> 
> Can we add additional options to the Iteration drop down and add dates to
> one existing one?
> - change existing "37.3" to "37.3- 1/13"
> - add "38.1- 1/27", "38.2- 2/10", "38.3- 2/24"

The dates are the end date of the iteration which always occurs on a Monday (each new Iteration starts on a Tuesday).  For the previously mentioned examples they would be:
37.3 - 1/12
38.1 - 1/26
38.2 - 2/09
38.3 - 2/23
(Assignee)

Comment 2

4 years ago
dates in the mm/dd format can be ambiguous outside of the US and i discourage their use.

are you ok with using the following format instead:

37.3 - 12 Jan
38.1 - 26 Jan
38.2 - 9 Feb
38.3 - 23 Feb

?
Flags: needinfo?(sescalante)
(Assignee)

Comment 3

4 years ago
note - we currently add new iteration values when we create new versions/milestones/flags just prior to an uplift/merge.  do you want us to keep the values in the iteration field one version ahead of the uplift in future, or is adding the values for 38 a week early a special case?
(In reply to Byron Jones ‹:glob› (limited availability until 19th jan) from comment #2)
> dates in the mm/dd format can be ambiguous outside of the US and i
> discourage their use.
> 
> are you ok with using the following format instead:
> 
> 37.3 - 12 Jan
> 38.1 - 26 Jan
> 38.2 - 9 Feb
> 38.3 - 23 Feb
> 
> ?

Yes, the date format you propose works fine.
Flags: needinfo?(sescalante)
(In reply to Byron Jones ‹:glob› (limited availability until 19th jan) from comment #3)
> note - we currently add new iteration values when we create new
> versions/milestones/flags just prior to an uplift/merge.  do you want us to
> keep the values in the iteration field one version ahead of the uplift in
> future, or is adding the values for 38 a week early a special case?

If I'm understanding you correctly we can have the new iteration values added just prior to the merge.  The new iteration (IT 38.1) starts on Tuesday January 13 so having all three '38' values for Monday January 12 is fine.
(Assignee)

Comment 6

4 years ago
(In reply to Marco Mucci [:MarcoM] from comment #5)
> If I'm understanding you correctly we can have the new iteration values
> added just prior to the merge.

yes - https://wiki.mozilla.org/BMO/new-version has the steps we perform, which include adding new iteration values (i've just updated that page to add the dates).

i've set a date on the 37.3 iteration and created the 38 values, but to avoid confusion i've left them disabled, ready to be activated just prior to the merge.
Assignee: nobody → glob
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.