Hi Gerald,
In my opinion at least if there is no target release for an activity don’t mark it with one. (leave it empty) This allows you to use tags for your own projects purposes and for the release activity to use tags for release purposes. No need to govern things in the release processes that do not need governance in that context. Also allows us to have parallel (and/or overlapping) tracked processes if necessary. / Chris From: <[email protected]> on behalf of "Kunzmann, Gerald" <[email protected]> Date: Friday 19 August 2016 at 11:17 To: David McBride <[email protected]>, "Beierl, Mark" <[email protected]> Cc: opnfv-project-leads <[email protected]>, TECH-DISCUSS OPNFV <[email protected]> Subject: Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][jira] JIRA process status report Hi David, What about tasks that a project is not planning to fix in Colorado, nor D release, but wants to keep the task as a reminder for a future release, i.e. the fix version is not clear yet? In Doctor and Promise we had left the “fixVersion” field empty for such cases. Which would be the recommended “fixVersion” version for such cases? Best regards, Gerald From: [email protected] [mailto:[email protected]] On Behalf Of David McBride Sent: Donnerstag, 18. August 2016 20:51 To: Beierl, Mark <[email protected]> Cc: [email protected]; [email protected] Subject: Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][jira] JIRA process status report Yes, all tasks, including sub-tasks. Thanks. David On Thu, Aug 18, 2016 at 11:30 AM, Beierl, Mark <[email protected]> wrote: 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 <[email protected]> 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: All JIRA issues must be assigned to a common version string, using the "fix version" field. Commit messages must include a reference to the issue ID. JIRA issue status should be updated whenever the status changes. 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 Email/Google Talk: [email protected] Skype: davidjmcbride1 IRC: dmcbride <08182016_opnfv_jira.txt>_______________________________________________ opnfv-project-leads mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-project-leads -- David McBride Release Manager, OPNFV Mobile: +1.805.276.8018 Email/Google Talk: [email protected] Skype: davidjmcbride1 IRC: dmcbride _______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
_______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
