[openstack-dev] [Fuel] New Criteria for UX bugs
xarses at gmail.com
Wed Jul 15 20:10:23 UTC 2015
I've updated the documentation on the wiki with this criteria
On Tue, Jul 14, 2015 at 4:22 PM Mike Scherbakov <mscherbakov at mirantis.com>
> Sounds good to start, we can always adjust later if needed. I actually
> changed one doc bug priority already using this criteria.
> On Fri, Jul 10, 2015 at 5:42 AM Jay Pipes <jaypipes at gmail.com> wrote:
>> On 07/09/2015 06:14 PM, Andrew Woodward wrote:
>> > We often have bugs which create really poor User eXperience (UX) but our
>> > current bug priority criteria prevent nearly all of them from being
>> > higher than medium (as they nearly always have workarounds). We need to
>> > identify what should qualify as a critical, or high UX defect so that
>> > they can receive appropriate attention.
>> > We discussed what this may look like on the IRC meeting, the general
>> > idea here is that the complexity of effort to work around the UX issue
>> > should be related to the priority.
>> > Critical: requires massive effort to work around, including [un|under]
>> > documented commands and edits to config files
>> > High: requires modification of config files, interfaces that users
>> > aren't expected to use (ie the API when it's _intended_ to work in the
>> > CLI / UI (exclusive of interfaces that are intended to only be available
>> > via API) or requires custom node yaml (again except when it should
>> > exclusively be available)
>> > Medium: Straight forward commands in the CLI
>> Above criteria look excellent to me, thanks Andrew!
>> OpenStack Development Mailing List (not for usage questions)
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> Mike Scherbakov
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
Fuel Community Ambassador
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev