This repository has been archived by the owner on Dec 13, 2020. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 34
Board window does not open via Sitemap menu #926
Comments
metas-mk
added a commit
to metasfresh/metasfresh
that referenced
this issue
Jun 22, 2017
Adding bugfix issue to this week's release notes: metasfresh/metasfresh-webui-frontend-legacy#926 Board window does not open via Sitemap menu
Tested. Works as required. Done/ Closing. |
metas-ts
added a commit
to metasfresh/metasfresh
that referenced
this issue
Jun 25, 2017
[#474](metasfresh/metasfresh-webui-api-legacy#474) Dashboard API: specify position when adding a new KPI/target indicator [metasfresh/metasfresh/issues#1814](#1814) Hide Processed flag from all M_InOut/Returns windows (webui) [#926](metasfresh/metasfresh-webui-frontend-legacy#926) Board window does not open via Sitemap menu [#470](metasfresh/metasfresh-webui-api-legacy#470) Cache image endpoint [#464](metasfresh/metasfresh-webui-api-legacy#464) Dashboard API: unify get available kpis/targetIndicators endpoints [#465](metasfresh/metasfresh-webui-api-legacy#465) Provide Endpoint w/ entry selections for given Breadcrumb [#864](metasfresh/metasfresh-webui-frontend-legacy#864) Show view sticky/readonly filters [#833](metasfresh/metasfresh-webui-frontend-legacy#833) Dashboard Window w/ Swimlane type functionalities [#1861](#1861) Performance degradation in HUKey.isReadonly() [#1873](#1873) Fix control amount and qty in payment data imported from camt.54 [#467](metasfresh/metasfresh-webui-api-legacy#467) board API: GET board/{boardId}/card?cardIds [#913](metasfresh/metasfresh-webui-frontend-legacy#913) Incompatible Sock.js versions me-45
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Type of issue
Bug
Current behavior
Currently, it is not possible to open the board window via Sitemap entry.
Expected behavior
Shall be opened when clicked in Sitemap Menu.
Steps to reproduce
Go to menu and click.
This is a follow-up of #833
The text was updated successfully, but these errors were encountered: