Represent Bug Status Values as Sets

Bug #959770 reported by Eike
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
bug-repo-syncer
New
Wishlist
Unassigned

Bug Description

The conversions between different systems of status values are ambiguous. In
many cases the values of certain status fields are undefined, or several values
are possible for a status field.

Therefore the status values should be represented with a set of possible
values, with a preferred or default value.

Before a merged bug is uploaded, it is compared to the cached version of
itself. If the value of the cached bug is in the set of the merged
bug, the two values are considered equal, and the value from the cached bug is
used as the default value.

Before uploading the bug, the set is exchanged by its default value.

See:
bug #949820

Eike (eike-welk)
Changed in bug-repo-syncer:
importance: Undecided → Wishlist
milestone: none → 0.4.0
description: updated
summary: - dummy
+ Represent Bug Status Values as Sets
Eike (eike-welk)
description: updated
Eike (eike-welk)
description: updated
Eike (eike-welk)
Changed in bug-repo-syncer:
milestone: 0.4.0 → 0.5.0
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.