Thanks Christian, appreciate you taking the time to fix them all manually. Sincerely, Nathan
From: Christian Gran [mailto:[email protected]] Sent: Wednesday, May 10, 2017 2:01 AM To: Nash, George <george.nash at intel.com>; Heldt-Sheller, Nathan <nathan.heldt-sheller at intel.com>; Way Vadhanasin <Wayakorn.Vadhanasin at microsoft.com>; iotivity-dev at lists.iotivity.org Subject: Re: [dev] JIRA doesn't clear "Resolution" field when issue is re-opened Hi, I have updated the workflow. Now by re-opening a ticket, the resolution is cleared. Unfortunately a bulk change for the resolution field is not possible - so I manually transitioned the tickets through re-open to clear it. If you see that your ticket was transitioned by me - this was the reason for it :-) thanks Christian On 9. May 2017, at 19:43, Nash, George <george.nash at intel.com<mailto:george.nash at intel.com>> wrote: I also agree there is no reason to have a ticket marked as fixed in one of the states you listed. George From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Heldt-Sheller, Nathan Sent: Tuesday, May 9, 2017 2:16 AM To: Christian Gran <gran at lynxtechnology.com<mailto:gran at lynxtechnology.com>>; Way Vadhanasin <Wayakorn.Vadhanasin at microsoft.com<mailto:Wayakorn.Vadhanasin at microsoft.com>>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] JIRA doesn't clear "Resolution" field when issue is re-opened For my part, I would say yes, bulk change them? I worry that an issue might be missed in RC2 if we don?t change re-opened tickets to not show as ?Fixed?. Thanks Christian, Nathan From: Christian Gran [mailto:[email protected]] Sent: Tuesday, May 9, 2017 1:47 AM To: Way Vadhanasin <Wayakorn.Vadhanasin at microsoft.com<mailto:Wayakorn.Vadhanasin at microsoft.com>>; Heldt-Sheller, Nathan <nathan.heldt-sheller at intel.com<mailto:nathan.heldt-sheller at intel.com>>; iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: Re: [dev] JIRA doesn't clear "Resolution" field when issue is re-opened Hi, I think to change the workflow is a good idea. But yes - this will only be triggered when the ticket is re-opened. Should we bulk change the 25 tickets, that right now have a resolution, but have been re-opened? See this filter: status in (Open, "In Progress", Reopened, Assigned) and resolution is not EMPTY thanks Christian On 8. May 2017, at 15:47, Way Vadhanasin via iotivity-dev <iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org>> wrote: I agree with Nathan. The current behavior bothers me as well. My ticket is https://jira.iotivity.org/browse/IOT-1871. In fact, either I don?t have permission to clear that field now that the issue is reopened or the issue is not in the right workflow to change. If we?re going with this plan, can we also fix the existing tickets that have been reopened without having to close and reopen to force the trigger? It appears the solution Nathan suggested (which I think is a good idea), only gets triggered when the issue is reopened. Thanks, Way From: iotivity-dev-bounces at lists.iotivity.org<mailto:iotivity-dev-bounces at lists.iotivity.org> [mailto:[email protected]] On Behalf Of Heldt-Sheller, Nathan Sent: Sunday, May 7, 2017 1:52 AM To: iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> Subject: [dev] JIRA doesn't clear "Resolution" field when issue is re-opened I?ve noticed that when I re-open an issue (via Workflow dropdown) it doesn?t change the Resolution, which remains ?Fixed?. This page suggests setting JIRA up to automatically clear the Resolution field when re-opened: https://confluence.atlassian.com/jirakb/how-to-clear-the-resolution-field-when-the-issue-is-reopened-648381467.html<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fconfluence.atlassian.com%2Fjirakb%2Fhow-to-clear-the-resolution-field-when-the-issue-is-reopened-648381467.html&data=02%7C01%7CWayakorn.Vadhanasin%40microsoft.com%7Cb470c91af7fe4cf6e35208d4952663b0%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636297439483797820&sdata=58tJJukfQk9w10%2F2MjZrhar5fMUES91c8vSpt2QMiMA%3D&reserved=0> Do folks (esp. Christian) think this is the right behavior? I?d like to get it set up because right now some issues appear incorrectly ?Fixed? when they are not (e.g. https://jira.iotivity.org/browse/IOT-1957<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fjira.iotivity.org%2Fbrowse%2FIOT-1957&data=02%7C01%7CWayakorn.Vadhanasin%40microsoft.com%7Cb470c91af7fe4cf6e35208d4952663b0%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636297439483797820&sdata=B%2F29%2FKSNrQbfokKoSdSMP6jmjhxmMoPw3IhERTfOKw4%3D&reserved=0>) Thanks, Nathan _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org<mailto:iotivity-dev at lists.iotivity.org> https://lists.iotivity.org/mailman/listinfo/iotivity-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.iotivity.org/pipermail/iotivity-dev/attachments/20170510/c4cb0b7c/attachment.html>
