Turns that there is a resolution overload in Jira. For any issue that was not transitioned into the closed state, the system sets the resolution field to "Unresolved".
As soon as the closure happens, the resolution field is set to one of the predefined resolutions (e.g. Out of Scope, Duplicate etc.). The introduction of Unresolved as predefined resolution overloads the meaning. Hence you needed the quotation. By definition a closed Jira task is resolved even if the customer may no consider it a resolution in the sense of the issue. Therefore I removed "Unresolved" as predefined resolution. I mapped the affected issues to "Won't do". They appear as resolved now. If there is any further clarification needed, please comment on https://bugreports.qt.io/browse/QTJIRA-373. -- Alex ________________________________________ From: Development <development-boun...@qt-project.org> on behalf of Jason McDonald <macadd...@gmail.com> Sent: Tuesday, 3 November 2020 05:00 To: development Subject: Re: [Development] Does anyone know why the Qt Bug Tracker has two "Unresolved" resolutions? On Tue, 3 Nov 2020 at 06:00, Oswald Buddenhagen <oswald.buddenha...@gmx.de<mailto:oswald.buddenha...@gmx.de>> wrote: On Tue, Nov 03, 2020 at 12:00:27AM +1000, Jason McDonald wrote: >Is there some obscure reason behind the duplicate resolution or is it a >mistake as I suspect? > certainly a mistake. note that "Fixed" is redundant with "Done", and was introduced as an unintended side effect of migrating issues from some internal workflow to the public one. maybe the "Unresolved" screw-up happened at the same time? Thanks Ossi. I will file a bug for this one too. Cheers, -- Dr. Jason McDonald (macadder on FreeNode) _______________________________________________ Development mailing list Development@qt-project.org https://lists.qt-project.org/listinfo/development
