Closed Bug 976926 Opened 10 years ago Closed 10 years ago

Please create a "One and Done" component

Categories

(bugzilla.mozilla.org :: Administration, task)

Production
task
Not set
normal

Tracking

()

VERIFIED FIXED

People

(Reporter: stephend, Assigned: dkl)

References

()

Details

Hi; we'd like a "One and Done" component in the QA product (for now/the forseeable future); the site is live, but not yet announced and in full operation, at: https://oneanddone.mozilla.org.  Its wiki page is: https://wiki.mozilla.org/QA/Taskboard

Name: "One and Done"
Product: QA
Component: One and Done
Description: For any issues and requests relating to the One and Done project's website/service

Versions:
* Version 1

Target Milestones:
* Milestone 1
* Milestone 2

Thanks!
Stephen. Are you asking for a new product called QA to be created and to contain a single component 'One and Done'? Or can we just add this to the existing product quality.mozilla.org instead as I would rather leverage an existing product rather than create a new one for one component.

dkl
Flags: needinfo?(stephen.donner)
(In reply to David Lawrence [:dkl] from comment #1)
> Stephen. Are you asking for a new product called QA to be created and to
> contain a single component 'One and Done'? Or can we just add this to the
> existing product quality.mozilla.org instead as I would rather leverage an
> existing product rather than create a new one for one component.
> 
> dkl

Doh, sorry; I meant: Classification: Other | Product: Mozilla QA | Component: One and Done
Flags: needinfo?(stephen.donner)
(In reply to Stephen Donner [:stephend] from comment #0)
> Hi; we'd like a "One and Done" component in the QA product (for now/the
> forseeable future); the site is live, but not yet announced and in full
> operation, at: https://oneanddone.mozilla.org.  Its wiki page is:
> https://wiki.mozilla.org/QA/Taskboard
> 
> Name: "One and Done"
> Product: QA
> Component: One and Done
> Description: For any issues and requests relating to the One and Done
> project's website/service

Component added to 'Mozilla QA' product.

> Versions:
> * Version 1
> 
> Target Milestones:
> * Milestone 1
> * Milestone 2

Did you need these added as well? Currently we have the following for Mozilla QA:

Versions: 	
unspecified

Milestones:
---
0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1.0
Future 

So the new values are not consistent with what is there already.

Thanks
dkl
Flags: needinfo?(stephen.donner)
Parul, can you chime in, here?  Thanks!
Flags: needinfo?(stephen.donner) → needinfo?(parul)
I think we need 

> Versions:
> * Version 1
> 
> Target Milestones:
> * Milestone 1
> * Milestone 2
Flags: needinfo?(parul)
(In reply to Parul Mathur [:pragmatic] from comment #5)
> I think we need 
> 
> > Versions:
> > * Version 1
> > 
> > Target Milestones:
> > * Milestone 1
> > * Milestone 2

So to further clarify, we need to do the following?

1) Add "Version 1" to the current version list so we have:

unspecified
Version 1

2) Add "Milestone 1" and "Milestone 2" to the list of milestones so we have:

0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1.0
Milestone 1
Milestone 2
Future 

OR should we make the current version list match exactly what is in comment 5? Other components in the Mozilla QA product may be using some of the current milestones we may not be able to remove some of them.

dkl
Flags: needinfo?(stephen.donner)
I think we need to do the following:

1) Add "Version 1" to the current version list so we have:

unspecified
Version 1

2) Add "Milestone 1" and "Milestone 2" to the list of milestones so we have:

0.1
0.2
0.3
0.4
0.5
0.6
0.7
0.8
0.9
1.0
Milestone 1
Milestone 2
Future
Ok. All done then.

dkl
Assignee: nobody → dkl
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(stephen.donner)
Resolution: --- → FIXED
Verified new component added for One and Done
Status: RESOLVED → VERIFIED
(In reply to Rebecca Billings [:rbillings] from comment #9)
> Verified new component added for One and Done

Thanks to all for taking care of this in my absence.  <3.
You need to log in before you can comment on or make changes to this bug.