other “non-release related”
Jira tasks out of those metrics.
/ Chris
From: on behalf of David McBride
Date: Monday 29 August 2016 at 20:46
To: "morgan.richo...@orange.com"
Cc: opnfv-project-leads , TECH-DISCUSS
OPNFV
Subject: Re: [opnfv-tech-discuss] [release][jira] JI
Hi Morgan,
Sorry - I should have been more clear. When I say "assigned", I mean
"assigned to a release" (i.e. the "fix version" field is NOT empty).
David
On Mon, Aug 29, 2016 at 4:04 AM, wrote:
> Hi,
>
> I am a bit surprised by the results.
>
> I reviewed the FUNCTEST JIRA.
> As far as I can
Hi,
I am a bit surprised by the results.
I reviewed the FUNCTEST JIRA.
As far as I can read I found only 14 JIRAs non assigned, all the others
are assigned.
For me, "assigned" means there is one person in the Assignee field, am I
wrong?
the non assigned JIRA corresponded to:
- D release
- Epic:
By the way, I just looked at the total (i.e. for all projects) number of
issues unresolved as compared to the total number of issues assigned to the
release. The ratio is 341 / 722, or abouit 47%. This means that less than
one month from the release, we've resolved less than half the issues
assig
Team,
Some updates for this week's report:
1. My script will how automatically add any missing versions to your
project, so you no longer need to worry about that task. To be clear, the
script simply makes the version strings available for selection in your
project. It does not assi
Team,
Gerald K raised a good point: what do you do in the event that you have an
issue that you want to document, but which won't be resolved until some
indefinite release in the future?
To deal with this case, I've added a version to all of the projects called
"Future Release". So, if you don'
Team,
As you know, I've been asking PTLs to update their JIRA projects to improve
accuracy and to enable use of JIRA as a project management tool. Note that
these updates will also improve the accuracy and relevance of JIRA reports
produced by Bitergia.
Essentially, I'm asking the team to follow
