[
https://issues.apache.org/jira/browse/OFBIZ-10722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jacques Le Roux updated OFBIZ-10722:
------------------------------------
Fix Version/s: (was: 18.12.01)
Affects Version/s: (was: Release Branch 18.12)
Hi Michael,
First I need to anwser Pierre's question again:
bq. So the 'Fixed Version(s) field should reference that is in r18? Otherwise
the ticket won't show up in the release notes when a release is cut from that
branch, right?
I previously answered
bq. Because when I fixed the trunk, and only it, the R18 branch did not exist.
So I could not put anything but Upcoming branch. I did not because it was still
a WIP. And I agree that now we should put 17.12.01 and 18.12.01. So this is a
peculiar case and we have no documentation about it yet. If you feel it should
be documented please complete
It was wrong. I removed Upcoming branch when I backported to R17 because R17
existed yet. But I never bacported to R18. So R18 should not be referenced
here. Else we would need to revisit all such cases, and anyway it makes no
sense.
The rule is: *We only put the branches where the fix has been backported into
the 'Fixed Version(s) field'*. There is no need to change the rules in the
wiki. And after removing R18 from Affects Version/s and 18.0.1 Fixed Version(s)
fields, this issue can be closed indeed.
> Date-find error when used in two forms of a same screen
> -------------------------------------------------------
>
> Key: OFBIZ-10722
> URL: https://issues.apache.org/jira/browse/OFBIZ-10722
> Project: OFBiz
> Issue Type: Bug
> Components: ALL COMPONENTS
> Affects Versions: Trunk, Release Branch 17.12
> Reporter: Leila Mekika
> Assignee: Jacques Le Roux
> Priority: Minor
> Fix For: 17.12.01
>
> Attachments: CsvFormMacroLibrary.ftl.rej, FoFormMacroLibrary.ftl.rej,
> HtmlFormMacroLibrary.ftl.rej, OFBIZ-10722.patch,
> TextFormMacroLibrary.ftl.rej, XlsFormMacroLibrary.ftl.rej,
> XmlFormMacroLibrary.ftl.rej
>
>
> When we have more than one form, in a screen, that use a date-find field, the
> second date-find picker is not working.
> To reproduce, you can add a new form with a date-find and call it below
> FindInvoices in FindInvoices screen
> Then load page [https://localhost:8443/accounting/control/findInvoices] . You
> should see that there is no picker on ne second date-find
>
> The patch adds an id that allow renderDateFindField macro script to work for
> both fields
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
