Hi everybody,
it's been a while since the last update[0] about the changes in Jira
going forward. As discussed in the review on Gerrit[1] and during last
year's contributors summit [2], the plan is to automate handling of Jira
issues in the Need More Information (NMI) state.
The automation rul
can issue the full
scope of possible issue transitions. You might want to add the additional
states to your board too.
--
Alex
From: Development
on behalf of Alex Blasche
Sent: Monday, 18 June 2018 1:08:35 PM
To: development@qt-project.org
: [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
day, 2 May 2018 2:18:54 PM
To: development@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 i
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
