459712 - Add 0.1..1.0 versions and target milestones to Mozilla Stats product

Status: VERIFIED FIXED

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

Description

[Daniel Einspanjer [:dre] [:deinspanjer]]

Is it possible to configure my account to be able to add things like milestones, versions, aliases, and keywords for this component?

If not, please set up the following:
Versions and Milestones -- we are currently working on release 0.3 of the dashboard system.  It would be useful to be able to set milestone versions through 1.0
0.1
0.2
...
0.9
1.0

Alias -- I don't know exactly what can/should go here.  Is this the whiteboard field?

Keywords:
Dashboard
Chart
Report
Pivot
ETL
Database

Comment 1

[Reed Loden [:reed]]

(In reply to comment #0)
> Is it possible to configure my account to be able to add things like
> milestones, versions, aliases, and keywords for this component?

While it is technically possible to allow this, we usually don't, as we already have a group of people who handle these changes for all of Bugzilla. We try to handle requests within a day or two, though.

> If not, please set up the following:
> Versions and Milestones -- we are currently working on release 0.3 of the
> dashboard system.  It would be useful to be able to set milestone versions
> through 1.0
> 0.1
> 0.2
> ...
> 0.9
> 1.0

I added 0.1 -> 1.0 versions and target milestones.

> Alias -- I don't know exactly what can/should go here.  Is this the whiteboard
> field?

No, aliases are per-bug aliases you can set to refer to a bug as a name/string rather than just the number. These are not regularly used unless there's a need.

> Keywords:
> Dashboard
> Chart
> Report
> Pivot
> ETL
> Database

Keywords are bugzilla-wide, so these additions wouldn't be appropriate. You could just make up some status whiteboard notes to use, or you could request more components to address these issues.

If this is all ok, feel free to resolve this bug.

Comment 2

[Daniel Einspanjer [:dre] [:deinspanjer]]

This works fine. Thanks for the explanation.

Comment 3

[timeless]

daniel: please consider removing the confidential flag. we don't make changes to bugzilla in the dark (all changes are logged in this component). reed's explanation to you is helpful to others who would have the same question.

Comment 4

[Daniel Einspanjer [:dre] [:deinspanjer]]

That's fine. I mostly made it confidential because the project itself is not visible to people outside of MoCo, so having a bug referencing a project other people couldn't see seemed odd.