ISISComputingGroup / ISISComputingGroup/IBEX

IBEX GUI: Group treeview by component type

Offen
#7,014 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
awaiting
Vorherrschende Sprache
Keine Sprachdaten
Sterne
6
Forks
2
Ø Merge
16 Std. 40 Min.
Gemergte PRs (30 T.)
2

Beschreibung

Following on from #6272 and then #7013 (which this ticket relies on) I would like to group the IOCs in the add/edit/remove IOC window by equipment type, matching what we do for the synoptic screens.

This ticket will involve an architectural discussion on how we should group the IOCs and use the existing mapping from the synoptic window, and whether this is stored appropriately in the database or just a file somewhere.

### Acceptance Criteria
_What is the acceptance criteria?_
- [ ] A discussion is had to talk about the best way of not duplicating work and sharing the mapping between equipment type and IOCs from the synoptic view
- [ ] A change is made to the tree view (if possible only in the edit component/configuration window) so that the equipment is grouped by type and then IOC type.
- [ ] System/squish tests are added for the above

### Extra Information
An example of how this could look in the treeview:

- IOCS:
- Motion Controllers:
- Galil Motion Controller:
- GALIL_01
- GALIL_02
- Mclennan Motion Controller:
- MCLENN_01
- MCLENN_02
- Temperature controllers:
- Eurotherm Temperature controller
- EUROTHRM_01
- EUROTHRM_02
- etc

## How to Test
(**Add before making a PR**)

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Rechercherichtung

Start by reading issues #6272 and #7013, then inspect the add/edit/remove IOC window and the existing synoptic-screen equipment-to-IOC mapping. Resolve where that mapping should live before changing the tree view to group equipment by type and IOC type. Add system/Squish tests covering the grouping and document how to test it.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Bewertung

Bereich
database, desktop, testing
Issue-Typ
Feature
Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Aktivitätsstatus
Veraltet
Klarheit
Muss geklärt werden
Anfängerfreundlichkeit
25/100

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.