Skip to content
This repository has been archived by the owner on Dec 23, 2019. It is now read-only.

When comparing releases with failed controls I want to see the performance index tied to a release as not controls are created equal. #94

Closed
willeybryan opened this issue May 30, 2019 · 1 comment
Labels
Performance-Index Features and issues relating to the risk indexing of controls and systems Web-Report The area of the software where the users can view their releases and controls in a browser

Comments

@willeybryan
Copy link
Collaborator

willeybryan commented May 30, 2019

Acceptance Criteria

Why?

  • I can glance at releases in the list I should be able to see which ones bring the most Performance to the product. In the future when we change the weighting of the controls it will bring more relevance, as for now, 9/10 controls will show 90% Performance which we accept as dumb, for now.
@willeybryan willeybryan added Web-Report The area of the software where the users can view their releases and controls in a browser Performance-Index Features and issues relating to the risk indexing of controls and systems labels May 30, 2019
@maxneuvians
Copy link
Contributor

Making some headway with this on #110

@willeybryan willeybryan changed the title When comparing releases with failed controls I want to see the level of risk the release carries as not controls are created equal. When comparing releases with failed controls I want to see the performance index tied to a release as not controls are created equal. Jun 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Performance-Index Features and issues relating to the risk indexing of controls and systems Web-Report The area of the software where the users can view their releases and controls in a browser
Projects
None yet
Development

No branches or pull requests

2 participants