Hey, David. Are you asking that all subtasks also be assigned to a version when you are doing your check for Unassigned Issues found? I only track fix version to the story level as subtasks are assigned to the story and it has a fix version.
Regards, Mark Mark Beierl | Advisory Solutions Architect Communication & Media Cloud – CTO Office EMC Federation +1 (613) 314-8106 @MarkBeierl On Aug 18, 2016, at 1:57 PM, David McBride <dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>> wrote: 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 four basic principles: 1. All JIRA issues must be assigned to a common version string, using the "fix version" field. 2. Commit messages must include a reference to the issue ID. 3. JIRA issue status should be updated whenever the status changes. 4. All JIRA issues assigned to a particular release must either be closed, or pushed out to a future release (i.e. update "fix version") by the release date. In order to track progress for 1 and 3, I've put together a script that pulls data from JIRA. The first report is attached. Please locate your project in the report and make plans to resolve any issues that are identified. Notes on the report: * "no versions" - indicates that the admin page contains no version strings for selection in the "fix version" field. * To fix this, add the common version strings to the "Versions" section on the project admin page. * "Version list NOT correct" - the project contains version strings, but is missing one or more of the common version strings. * All projects must use the common set of version strings. * "Unassigned issues found: [list]" - the project has issues where the "fix version" field is empty. * Remember, all issues must be assignee to a version, using the "fix version" field. * About 85% of the projects have unassigned issues. * There are two solutions to this: (a) educate your project team to set the field when they create the ticket; (b) when you conduct a bug scrub, or triage, search your JIRA project for issues that are unassigned and update them. Kudos! Note that the Domino, Models, and IPv6 projects all have the correct version list and no unassigned issues. An inspiration to us all :) Final note: this script is new, so it wouldn't surprise me if there are errors. If you see something that doesn't make sense, please let me know. David -- David McBride Release Manager, OPNFV Mobile: +1.805.276.8018<tel:%2B1.805.276.8018> Email/Google Talk: dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org> Skype: davidjmcbride1 IRC: dmcbride <08182016_opnfv_jira.txt>_______________________________________________ opnfv-project-leads mailing list opnfv-project-le...@lists.opnfv.org<mailto:opnfv-project-le...@lists.opnfv.org> https://lists.opnfv.org/mailman/listinfo/opnfv-project-leads
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
