This is fantastic, thank you @Donal for leading the initiative to get this
improvement made!
On 8/27/20, 9:49 AM, "Donal Evans" <doev...@vmware.com> wrote:
The proposed changes have now been applied to the GEODE Jira. Hopefully it
will now be easier for people to input the relevant information at time of
ticket creation.
________________________________
From: Mark Bretl <mbr...@apache.org>
Sent: Tuesday, August 18, 2020 2:38 PM
To: geode <dev@geode.apache.org>
Subject: Re: [PROPOSAL] Remove "Fix Version/s" and "Sprint" from Jira
"Create Issue" dialogue and include "Affects Version/s"
+1
--Mark
On Tue, Aug 18, 2020 at 9:39 AM Raymond Ingles <ring...@vmware.com> wrote:
> +1
>
> On 8/17/20, 3:04 PM, "Donal Evans" <doev...@vmware.com> wrote:
>
> Looking at the dialogue that opens when you attempt to create a new
> ticket in the GEODE Jira[1], there are two fields included that aren't
> really necessary and may cause confusion. The "Fix Version/s" field should
> presumably not be filled out until the issue has actually been fixed,
> rather than at the time of ticket creation. The "Sprint" field seems to no
> longer serve any purpose at all that I can discern, having only been
filled
> in 13 tickets, the most recent of which was created in December 2018[2].
> With the expansion of the community contributing to the Geode project,
it's
> important to provide a straightforward experience for people who are new
to
> the project and wish to file tickets, so the presence of these fields may
> cause issues.
>
> I propose that these two fields be removed from the "Create Issue"
> dialogue and that the "Affects Version/s" field be added, since that field
> is far more important at time of ticket creation. There are currently 3851
> bug tickets in the Jira with no "Affects Version/s" value entered at
> all[3], which I suspect is in part due to that field not being an option
in
> the "Create Issue" dialogue, meaning you have to remember to go back after
> creating the ticket and enter it. With Geode moving to a model of having
> support branches and patch releases, properly capturing the versions
> affected by a given issue becomes even more important.
>
> [1]
>
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fi.imgur.com%2FoQ8CW87.png&data=02%7C01%7Conichols%40vmware.com%7C986bc2d30d3b408e31a608d84aa921a6%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637341437561225893&sdata=TnQjzy1DV8BkOPJ5AY7iX61AYxZeh5tRsmkV7WckpjA%3D&reserved=0
> [2]
>
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fprojects%2FGEODE%2Fissues%2FGEODE-8433%3Ffilter%3Dallissues%26orderby%3Dcf%255B12310921%255D%2BASC%252C%2Bcreated%2BDESC&data=02%7C01%7Conichols%40vmware.com%7C986bc2d30d3b408e31a608d84aa921a6%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637341437561225893&sdata=HrqUrDH2fO63NTrUdGl%2FkuCFOt40PRNAIkYMfzOY%2BSM%3D&reserved=0
> [3]
>
https://nam04.safelinks.protection.outlook.com/?url=https%3A%2F%2Fissues.apache.org%2Fjira%2Fbrowse%2FGEODE-8433%3Fjql%3Dproject%2520%253D%2520GEODE%2520AND%2520issuetype%2520%253D%2520Bug%2520AND%2520affectedVersion%2520%253D%2520EMPTY%2520ORDER%2520BY%2520created%2520DESC%252C%2520affectedVersion%2520ASC%252C%2520cf%255B12310921%255D%2520ASC&data=02%7C01%7Conichols%40vmware.com%7C986bc2d30d3b408e31a608d84aa921a6%7Cb39138ca3cee4b4aa4d6cd83d9dd62f0%7C0%7C0%7C637341437561225893&sdata=CJI2WlIBwnbgvx5cvENtc70HdozQSRXncJVaqllhn5M%3D&reserved=0
>
>
