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.com>wrote: >> >>> 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
