ISISComputingGroup / ISISComputingGroup/IBEX

IBEX GUI: Group treeview by component type

Aperta
#7,014 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub
awaiting
Lingua principale
Nessun dato sulla lingua
Stelle
6
Fork
2
Merge medio
16h 40m
PR unite (30g)
2

Descrizione

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**)

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Ambito
database, desktop, testing
Tipo di issue
Funzionalità
Difficoltà
5/5
Tempo stimato
Più di una settimana
Stato di attività
Ferma
Chiarezza
Da chiarire
Idoneità per principianti
25/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.