You are seeing the non-series task status. That is meant to be synchronised with the series specific task. So either that has failed, or there is a means to generate out of sync non-series status - e.g. by changing the series that it is associated with (or more recently permitting deletions of tasks).
Indeed, looking at the bug history:
2012-04-03 14:35:58 Natalia Bidart ubuntuone-control-panel/trunk: status New Fix Released
2012-04-04 16:05:01 Natalia Bidart bug task deleted ubuntu-sso-client
2012-04-04 16:05:17 Natalia Bidart bug task added ubuntuone-control-panel
So - this isn't a regression (because similar mismatches have long been possible), but it is yet another symptom of conjoined masters being complex.
You are seeing the non-series task status. That is meant to be synchronised with the series specific task. So either that has failed, or there is a means to generate out of sync non-series status - e.g. by changing the series that it is associated with (or more recently permitting deletions of tasks).
Indeed, looking at the bug history: control- panel/trunk: status New Fix Released control- panel
2012-04-03 14:35:58 Natalia Bidart ubuntuone-
2012-04-04 16:05:01 Natalia Bidart bug task deleted ubuntu-sso-client
2012-04-04 16:05:17 Natalia Bidart bug task added ubuntuone-
So - this isn't a regression (because similar mismatches have long been possible), but it is yet another symptom of conjoined masters being complex.