RE: [Discuss] Old imported JIRA issues
Well on the adobe side the [1] is status of community and doesn't have any way to test the bug, however it linked to [2] which was the exact same bug and it was closed. However I did personally test the code given and it produced correct results. [1] http://bugs.adobe.com/jira/browse/SDK-16396 [2] https://bugs.adobe.com/jira/browse/SDK-11282 -Mark -Original Message- From: Alex Harui [mailto:aha...@adobe.com] Sent: Tuesday, April 16, 2013 11:17 PM To: dev@flex.apache.org Subject: Re: [Discuss] Old imported JIRA issues I had to write my own export/import tool because Adobe is on an older and highly customized version of JIRA, and we also had to filter out security related issues. It is entirely possible there were bugs in it. But the issue you posted here does look closed to me. Am I missing something, or can you point me to another issue? On 4/16/13 5:14 PM, Mark Kessler kesslerconsult...@gmail.com wrote: Forgot to leave an example URL [1]. There are a total of 28 more of them that I could knock out if so. [1] https://issues.apache.org/jira/browse/FLEX-15274 On Tue, Apr 16, 2013 at 8:01 PM, Mark Kessler kesslerconsult...@gmail.comwrote: The very old JIRA issues imported from Adobe are missing attachments (can go to original adobe bug and find some of them). But more importantly, there are a few that have comments from the import like[1]... If the comments say the original resolution is fixed. Can we mark the issue fixed on our flex issues for these old ones? [1] Adobe JIRA added a comment - 27/Jan/12 04:08 Adobe Bug URL: http://bugs.adobe.com/jira/browse/SDK-16396 Original Reporter: mitek17 Original Resolution: Fixed Discoverability: High Number of votes: 0 Reproducibility: Every Time Severity: Incorrectly Functioning reporter: mitek17 -Mark -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [Discuss] Old imported JIRA issues
Hi, However I did personally test the code given and it produced correct results. Put the test code into JIRA if you can - means someone can easily retest if needed at a future date. Thanks, Justin
[Discuss] Old imported JIRA issues
The very old JIRA issues imported from Adobe are missing attachments (can go to original adobe bug and find some of them). But more importantly, there are a few that have comments from the import like[1]... If the comments say the original resolution is fixed. Can we mark the issue fixed on our flex issues for these old ones? [1] Adobe JIRA added a comment - 27/Jan/12 04:08 Adobe Bug URL: http://bugs.adobe.com/jira/browse/SDK-16396 Original Reporter: mitek17 Original Resolution: Fixed Discoverability: High Number of votes: 0 Reproducibility: Every Time Severity: Incorrectly Functioning reporter: mitek17 -Mark
Re: [Discuss] Old imported JIRA issues
Forgot to leave an example URL [1]. There are a total of 28 more of them that I could knock out if so. [1] https://issues.apache.org/jira/browse/FLEX-15274 On Tue, Apr 16, 2013 at 8:01 PM, Mark Kessler kesslerconsult...@gmail.comwrote: The very old JIRA issues imported from Adobe are missing attachments (can go to original adobe bug and find some of them). But more importantly, there are a few that have comments from the import like[1]... If the comments say the original resolution is fixed. Can we mark the issue fixed on our flex issues for these old ones? [1] Adobe JIRA added a comment - 27/Jan/12 04:08 Adobe Bug URL: http://bugs.adobe.com/jira/browse/SDK-16396 Original Reporter: mitek17 Original Resolution: Fixed Discoverability: High Number of votes: 0 Reproducibility: Every Time Severity: Incorrectly Functioning reporter: mitek17 -Mark
Re: [Discuss] Old imported JIRA issues
Hi, The very old JIRA issues imported from Adobe are missing attachments (can go to original adobe bug and find some of them). It's a know issue - infra and Alex have been working on it for some time. But more importantly,there are a few that have comments from the import like[1]... If the comments say the original resolution is fixed. Can we mark the issue fixed on our flex issues for these old ones? A large number of Adobe issue were marked as fixed (although usually closed and later) when they were just deferred. https://issues.apache.org/jira/issues/?filter=12321179 These seem to quite a few issues in this other state. https://issues.apache.org/jira/issues/?filter=12323883 Do we know the reason why they are open? ie did the JIRA import have some issues or where they open in the Adobe JIRA for some reason when imported? My guess from looking at a few of them is that most of them may not be fixed but refer to older version of the SDK or may not be relevant any more in some cases. Thanks, Justin
Re: [Discuss] Old imported JIRA issues
Well worst case scenario I can start testing the 1,006... which can be done more quickly if most of them have already been addressed in Adobe jira in some fasion. Was hoping to not duplicate work :) Thanks Justin. -Mark On Tue, Apr 16, 2013 at 8:40 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, The very old JIRA issues imported from Adobe are missing attachments (can go to original adobe bug and find some of them). It's a know issue - infra and Alex have been working on it for some time. But more importantly,there are a few that have comments from the import like[1]... If the comments say the original resolution is fixed. Can we mark the issue fixed on our flex issues for these old ones? A large number of Adobe issue were marked as fixed (although usually closed and later) when they were just deferred. https://issues.apache.org/jira/issues/?filter=12321179 These seem to quite a few issues in this other state. https://issues.apache.org/jira/issues/?filter=12323883 Do we know the reason why they are open? ie did the JIRA import have some issues or where they open in the Adobe JIRA for some reason when imported? My guess from looking at a few of them is that most of them may not be fixed but refer to older version of the SDK or may not be relevant any more in some cases. Thanks, Justin
Re: [Discuss] Old imported JIRA issues
Good point about marking some as easyfix. I've labeled up those ones you listed. On Tue, Apr 16, 2013 at 9:09 PM, Justin Mclean jus...@classsoftware.comwrote: Hi, Well worst case scenario I can start testing the 1,006... Well don't let me stop you. :-) Perhaps if mark some with easyfix or easytest so other committers/users can help out. Some issues would be very easy to validate, for instance: https://issues.apache.org/jira/browse/FLEX-26698 - Currency format issue when formatting 0 https://issues.apache.org/jira/browse/FLEX-20322 - French locale issue with month names https://issues.apache.org/jira/browse/FLEX-17869 - Hand cursor on link bar https://issues.apache.org/jira/browse/FLEX-16714 - Issue with credit card validator On locale issues this is an interesting french locale issue: https://issues.apache.org/jira/browse/FLEX-27235 Thanks, Justin
Re: [Discuss] Old imported JIRA issues
I had to write my own export/import tool because Adobe is on an older and highly customized version of JIRA, and we also had to filter out security related issues. It is entirely possible there were bugs in it. But the issue you posted here does look closed to me. Am I missing something, or can you point me to another issue? On 4/16/13 5:14 PM, Mark Kessler kesslerconsult...@gmail.com wrote: Forgot to leave an example URL [1]. There are a total of 28 more of them that I could knock out if so. [1] https://issues.apache.org/jira/browse/FLEX-15274 On Tue, Apr 16, 2013 at 8:01 PM, Mark Kessler kesslerconsult...@gmail.comwrote: The very old JIRA issues imported from Adobe are missing attachments (can go to original adobe bug and find some of them). But more importantly, there are a few that have comments from the import like[1]... If the comments say the original resolution is fixed. Can we mark the issue fixed on our flex issues for these old ones? [1] Adobe JIRA added a comment - 27/Jan/12 04:08 Adobe Bug URL: http://bugs.adobe.com/jira/browse/SDK-16396 Original Reporter: mitek17 Original Resolution: Fixed Discoverability: High Number of votes: 0 Reproducibility: Every Time Severity: Incorrectly Functioning reporter: mitek17 -Mark -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [Discuss] Old imported JIRA issues
Hi, It is entirely possible there were bugs in it. I've come across one issue that was misisng it's description but other than the few minor things discussed way back it seemed to have mostly worked. But the issue you posted here does look closed to me. Am I missing something, or can you point me to another issue? Think that issue is actually closed and fixed but try this list: https://issues.apache.org/jira/issues/?filter=12323883 Justin
Re: [Discuss] Old imported JIRA issues
Nevermind, I saw you closed it. I think my import/export tool didn't handle status=community and maybe some other scenarios. So it may be that open-but-fixed means community-and-not-fixed. When I look at the Adobe JIRA issue it doesn't appear fixed. -Alex On 4/16/13 8:16 PM, Alex Harui aha...@adobe.com wrote: I had to write my own export/import tool because Adobe is on an older and highly customized version of JIRA, and we also had to filter out security related issues. It is entirely possible there were bugs in it. But the issue you posted here does look closed to me. Am I missing something, or can you point me to another issue? On 4/16/13 5:14 PM, Mark Kessler kesslerconsult...@gmail.com wrote: Forgot to leave an example URL [1]. There are a total of 28 more of them that I could knock out if so. [1] https://issues.apache.org/jira/browse/FLEX-15274 On Tue, Apr 16, 2013 at 8:01 PM, Mark Kessler kesslerconsult...@gmail.comwrote: The very old JIRA issues imported from Adobe are missing attachments (can go to original adobe bug and find some of them). But more importantly, there are a few that have comments from the import like[1]... If the comments say the original resolution is fixed. Can we mark the issue fixed on our flex issues for these old ones? [1] Adobe JIRA added a comment - 27/Jan/12 04:08 Adobe Bug URL: http://bugs.adobe.com/jira/browse/SDK-16396 Original Reporter: mitek17 Original Resolution: Fixed Discoverability: High Number of votes: 0 Reproducibility: Every Time Severity: Incorrectly Functioning reporter: mitek17 -Mark -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [Discuss] Old imported JIRA issues
Hi, I wonder if there's a way to mass update all of those issues? Yes JIRA can do that but what do you want changed? The only minor issue I see is the Original Resolution: Fixed text in the comments but the JIRA issue itself is in the correct state. Justin
Re: [Discuss] Old imported JIRA issues
On Apr 16, 2013 8:40 PM, Alex Harui aha...@adobe.com wrote: OK, in a quick sample, open-but-fixed-in-the-comments seems to be mapping to status=community or status=internalreview, which means that these are not fixed. I wonder if there's a way to mass update all of those issues? -Alex Please turn off email notifications when doing mass updates. Pretty please? Thanks, Om On 4/16/13 8:32 PM, Alex Harui aha...@adobe.com wrote: Nevermind, I saw you closed it. I think my import/export tool didn't handle status=community and maybe some other scenarios. So it may be that open-but-fixed means community-and-not-fixed. When I look at the Adobe JIRA issue it doesn't appear fixed. -Alex On 4/16/13 8:16 PM, Alex Harui aha...@adobe.com wrote: I had to write my own export/import tool because Adobe is on an older and highly customized version of JIRA, and we also had to filter out security related issues. It is entirely possible there were bugs in it. But the issue you posted here does look closed to me. Am I missing something, or can you point me to another issue? On 4/16/13 5:14 PM, Mark Kessler kesslerconsult...@gmail.com wrote: Forgot to leave an example URL [1]. There are a total of 28 more of them that I could knock out if so. [1] https://issues.apache.org/jira/browse/FLEX-15274 On Tue, Apr 16, 2013 at 8:01 PM, Mark Kessler kesslerconsult...@gmail.comwrote: The very old JIRA issues imported from Adobe are missing attachments (can go to original adobe bug and find some of them). But more importantly, there are a few that have comments from the import like[1]... If the comments say the original resolution is fixed. Can we mark the issue fixed on our flex issues for these old ones? [1] Adobe JIRA added a comment - 27/Jan/12 04:08 Adobe Bug URL: http://bugs.adobe.com/jira/browse/SDK-16396 Original Reporter: mitek17 Original Resolution: Fixed Discoverability: High Number of votes: 0 Reproducibility: Every Time Severity: Incorrectly Functioning reporter: mitek17 -Mark -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [Discuss] Old imported JIRA issues
On 4/16/13 8:45 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, I wonder if there's a way to mass update all of those issues? Yes JIRA can do that but what do you want changed? The only minor issue I see is the Original Resolution: Fixed text in the comments but the JIRA issue itself is in the correct state. Yeah, good point. I wonder if there is a way to mass edit the comments. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [Discuss] Old imported JIRA issues
HI, Please turn off email notifications when doing mass updates. If you referring to the easyfix/easytest tags that are individual edits and not considered a mass update. There's no way to turn email notification off for a tag edit field that I know of. Should only be a dozen or so more. Thanks, Justin
Re: [Discuss] Old imported JIRA issues
On Apr 16, 2013 8:56 PM, Justin Mclean jus...@classsoftware.com wrote: HI, Please turn off email notifications when doing mass updates. If you referring to the easyfix/easytest tags that are individual edits and not considered a mass update. There's no way to turn email notification off for a tag edit field that I know of. Yes, I was referring to that as well. Can't we just turn it off for a while, do the edits and then turn it on? Thanks, Om Should only be a dozen or so more. Thanks, Justin
Re: [Discuss] Old imported JIRA issues
Hi, Yes, I was referring to that as well. Can't we just turn it off for a while, do the edits and then turn it on? Even though I'm an JIRA admin I can't edit the JIRA notifications - we need to get infra to turn off and on again I believe. During that time we may miss notification of edited to existing issues, new issues etc etc so probably not realistically possible. All done now (for now) BTW. Justin
