[Interest] Jira changes going forward

[Alex Blasche]

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