Versions Compared
compared with
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Comment:
Repair Jira Macros
Attendees
Jacques Marais, Dirk Roets , Andrew Butchart (Unlicensed) , Charl Viljoen , Former user (Deleted) , Christine Hansmann , Nyameko Mateke , Danie Kotzé , Former user (Deleted) , Charles Rethman (Unlicensed) , Desmond van den Heever (Unlicensed) , Johan Grundling , Siphenkosi Filtane , Johan Snyman (Unlicensed) , Torbjørn Kristoffersen , Former user (Deleted)
Helium Development Roadmap & Progress
Discussion Topics
Helium Dev
- Related to Helium 1.x Tableau embedding
Jira Legacy server Jira serverId c64e0283-89f7-3f2d-803a-d01a11949037 key HE-9423
IoT
- Localisation of Jasper reports by injecting Java into Jasper Reports
- https://wikimezzaninewiki.mezzaninewareatlassian.comnet/wiki/x/HgPOBQe5l3
- Troublesome (very slow) deployments due to scripts that create materialised views
- Proposal to not drop views as part of deployment
- Proposal to create materialised view with no data during deployment
- Clarification on when Helium does schema upgrades: Any upgrade that changes the internal hash representing the data model and sql scripts
SVS
- Feature request:
Jira Legacy showSummary false server Jira serverId c64e0283-89f7-3f2d-803a-d01a11949037 key HE-9424
eLABS
- Issue where front-end seemingly times out before the configured time (as configured for the Helium process monitor). Back-end process keeps running. Issue is intermittent, and does not seem to correlate with load on the Platform.
- Suggestion was to create a Jira ticket to be treated as a Support Request / Fault.
Jira Legacy server Jira serverId c64e0283-89f7-3f2d-803a-d01a11949037 key HE-9427
- Suggestion was to create a Jira ticket to be treated as a Support Request / Fault.
CF+
- Suggestion for an additional discussion on
- the data export service (for CSV exports) and
- potentially implementing CSV uploads for Helium 2 based product
DevOps & Rest of Operations
- Suggestion to all teams to consider using CREATE INDEX CONCURRENTLY when creating indexes (to avoid table level locks).
- Mention of front-end components / framework being developed as part of the MFW 2 development effort.
- Operational challenges related to eLabs enrolments.