remove % complete for cycles

RESOLVED FIXED

Status

Mozilla QA
MozTrap
--
enhancement
RESOLVED FIXED
7 years ago
6 years ago

People

(Reporter: camd, Unassigned)

Tracking

Details

(Reporter)

Description

7 years ago
% complete for cycles currently doesn't show what one might expect.  And I now question if it's valid to think of % complete for a cycle, since new runs will be added to it over the course of its life.  This means the % complete isn't something linear that can be measured, it'll go up and down getting near completion when the last test run is getting close to done, then going away from completion when a new run is added for a new build.

% complete is perfectly valid on test runs, since they're likely to be mostly determined at time of creation.

test runs don't currently take product build versions into account, but that's a separate story.
(Reporter)

Comment 1

7 years ago
A Pivotal Tracker story has been created for this Bug: http://www.pivotaltracker.com/story/show/20703679
(Reporter)

Comment 2

7 years ago
Eric Meyer changed story state to started in Pivotal Tracker
(Reporter)

Comment 3

7 years ago
Eric Meyer changed story state to finished in Pivotal Tracker
(Reporter)

Comment 4

7 years ago
Carl Meyer added a comment in Pivotal Tracker:   
   
Cycle results need to be removed from the finder as well.
(Reporter)

Comment 5

7 years ago
Carl Meyer changed story state to started in Pivotal Tracker
(Reporter)

Comment 6

7 years ago
Eric Meyer changed story state to finished in Pivotal Tracker
(Reporter)

Comment 7

7 years ago
Carl Meyer changed story state to delivered in Pivotal Tracker
(Reporter)

Comment 8

7 years ago
Cameron Dawson changed story state to accepted in Pivotal Tracker
(Reporter)

Updated

6 years ago
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.