[Development] Jira changes going forward

[Alex Blasche]

The last disruptive change is about to happen. The upcoming changes concern the workflows:

1.) The workflow for requirements (Epic, User Story, Change Requests) related issues will be streamlined. The "Implemented" & "Verified" states (served no purpose anymore) will be removed and a "Blocked" state is introduced. The "Blocked" state is meant to be used to when some external  (to the developer) conditions or dependencies are not met. Note that a blocked issue still maintains the "unresolved" resolution. 

2.) The bug workflow is made a bit more convenient by introducing the direct transitons to the "Need more info" state. So far only "Reported" issues could transition to NMI. "Open" and "In progress" will obtain the same right.

The changes have the nice side effect that Kanban boards can issue the full scope of possible issue transitions. You might want to add the additional states to your board too.

--
Alex




________________________________________
From: Development <development-bounces+alexander.blasche=qt.io at qt-project.org> on behalf of Alex Blasche <alexander.blasche at qt.io>
Sent: Monday, 18 June 2018 1:08:35 PM
To: development at qt-project.org; interest at qt-project.org Interest
Subject: Re: [Development] Jira changes going forward

This implementation has started. Please be aware of changing component names.

--
Alex

________________________________________
From: Development <development-bounces+alexander.blasche=qt.io at qt-project.org> on behalf of Alex Blasche <alexander.blasche at qt.io>
Sent: Thursday, 31 May 2018 2:42:51 PM
To: development at qt-project.org; interest at qt-project.org Interest
Subject: Re: [Development] Jira changes going forward

This review has come to a conclusion. Based on reviews the major points have settled. The highlights of the changes are:

- Internal Qt company requirements management will shift to public projects
- Renaming and reordering of components (breaks existing filters)
- Additional fields for Jira issues
- Automatic closure/check of long pending "Need more Info" bugs where the bug reporter fails to provide information

Implementation of those changes will happen during June.

--
Alex


________________________________________
From: Development <development-bounces+alexander.blasche=qt.io at qt-project.org> on behalf of Alex Blasche <alexander.blasche at qt.io>
Sent: Wednesday, 2 May 2018 2:18:54 PM
To: development at qt-project.org
Subject: [Development] Jira changes going forward

Hi,

there are quite a few changes to Jira on my todo list. Some of them result from some internal TQtC process changes (related to public requirements mgmt) and others were put forward by individuals with a keen interest in improving things (thank you for that). Unfortunately some of proposals will break existing setups (especially filters).

Since there are a lot of changes I chose to use gerrit for the discussion. A long mail is not able to provide the means to update and review the latest consensus. Please have a look at

https://codereview.qt-project.org/#/c/225694/

The patch is not intended to be merged. It merely exists to facilitate the community discussion. However I might document some of the outcomes (especially process outcomes) somewhere later on.


Thank you for your feedback.
--
Alex

_______________________________________________
Development mailing list
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________
Development mailing list
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development
_______________________________________________
Development mailing list
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development