Apache OpenOffice (AOO) Bugzilla – Issue 102564
Linked image not shown in form
Last modified: 2009-09-05 16:59:15 UTC
New feature introduced in issue 91310, which was working in OOo 3.1, image control bounded to text field, containing link to the images to the file system, not working in DEV32m49 version. Create new odb file in OOo 3.1, create table with text field to store link, and form with image control bounded to text field, insert picture, link to file system any image file, store record in table, save file, close. Open odb file with DEV32m49, open form no picture shown in form, check table, the link to image file exests. Regression.
confirming, grabbing, targeting, setting "regression keyword"
fixed in CWS dba32e find more information about this CWS, like when it is available in the master builds, in EIS, the Environment Information System: http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fdba32e
seeing this I am courious about when this can be expected to be in real-life ( while he foregoing cws dba32c and d) did not got quality-approval until now. Martin
mhatheoo: dba32e, where this is fixed, will probably go to QA this week. We'll see.
fs->msc: please verify in CWS dba32e
verified in CWS dba32e find more information about this CWS, like when it is available in the master builds, in EIS, the Environment Information System: http://eis.services.openoffice.org/EIS2/cws.ShowCWS?Path=DEV300%2Fdba32e
msc: question please: isn't it, that an issue should be set to fixed only, when the build of the related CWS (not to think about integration into the master) is completed successfully? Martin
fs->mhatheoo: The issue is set to FIXED by the developer who commits the fix to a CWS, after committing. QA sets it to VERIFIED after verifying the fix in the CWS. There's diagrams for this somewhere at http://qa.openoffice.org/issue_handling/ ...
>fs well yes, that is, what I had in mind, and thats what I asked: what is the situation, when the fixing had reached the qa-one-level and was set to fixed, but finally the integration to the related CWS failed, because the complete CWS failed. The point to set an issue to closed, is correct at the very end, but what happend on the way to that? I see the workflow-scheme for qa as weak, because it does not handle the withdrawl of the status of the details (issues), when integration to the next step (CWS) failed. sorry, this is not about this issue, this is about qualtity-management, but I see this as part of finalizing of issues - in general.
Hmm, I am not sure I get you here. Also, as you say, this is more about the QA/issue work flow in general - care to ask the question on dev@qa.openoffice.org? (side note: dba32e is approved meanwhile. Just because the CWS failed in the first QA pass, doesn't mean it's dead forever.)
Checked in OOo Dev32m57, form showing linked image. Closed.