2.0 - maintenance 57% 14 issues (8 closed — 6 open) Related issues Bug #3952: Forms: heading are not shown when the first item of the section is hidden Actions Bug #4004: Crash when trying to modify a FIND with a read-only account Actions Bug #4213: PERSON DIRECTORY : manual fusion not working Actions Bug #4512: DOCS / DOCS types : Hierarchical types are not applied on request (doc search) Actions Feature #3763: Debian package for v2 (stretch) Actions Feature #3950: Sites - Shortcut menu availability Actions
2.1 24% 129 issues (31 closed — 98 open) Related issues Bug #3661: IMPORT PARCELS : public domain type is not compulsory Actions Bug #3726: Sheetfile STATS : number of parcel is not OK Actions Bug #4058: ODT template: processing is slow. Image is not available Actions Bug #4059: Full search: no index on item import Actions Bug #4079: Context record relation listing: only one line of each right relation member is displayed Actions Bug #4183: Incorrect deletion of warehouse's division when deleting an import Actions Bug #4184: Reference importers: correct target images__image by documents__image Actions Bug #4185: Reference importers: add discovery date taq Actions Bug #4230: Search bookmark: no possibility to remove a bookmark Actions Bug #4238: Finds criteria search: sites instead of entities Actions Bug #4241: Warehouse sheet: wrong display of the address Actions Bug #4275: Treatment request : docs not listed in Sheet-file Actions Bug #4276: Treatment request : treatments not listed in Sheet-file Actions Bug #4278: OPE sheet-file : Numerical ressource (web address) no more listed Actions Bug #4301: Sheets: subsections' titles should'nt appear when all subsection's fields are blank Actions Bug #4305: Containers' modification: remove the "Validate and end" button on the first wizard's panel Actions Bug #4328: SITES sheet: the rapid link (pencil icon) for modification is missing Actions Bug #4402: Finds criteria search: id of reference container doesn't work Actions Bug #4436: SRID types are missing on a new installation Actions Bug #4451: A search on several towns (with several results for each of them) gives no results (without a django error) Actions Bug #4454: MAP : GPS error circle prevent the user for querying map objects Actions Bug #4467: MAP MODULE : maps are displayed even with the MAP MODULE unselected (DJANGO ADMIN) Actions Bug #4479: CONTEXT RECORD creation from OPERATION sheetfile : UE could be create without parcel even on Instances where parcels are compulsory Actions Bug #4499: Automatic persons merge doesn't detect duplicates when one of them has no organisation Actions Bug #4513: Main image: no automatic main image after import when a previous main image has been deleted Actions Bug #4515: DOCS / ADD or MODIFY : second author added (not in th DB before) erase previouly selected author Actions Bug #4519: Target keys linked to a type should be removed with this type Actions Bug #4520: Imports should be archived in (ante-)chronological order Actions Bug #4542: Basket sheet: order persons (with whom the basket is shared) by alphabetical order Actions Bug #4552: Warehouse deletion also delete associated container Actions Bug #4554: Administrativ act: no warning on associated item deletion Actions Bug #4555: Treatments: treatment is not deleted when the only associated find is deleted Actions Bug #4580: Directory > Person: when a search is pinned, going to "Manual merge" crashes silently Actions Feature #3077: OPE / CONTEXT RECORD / FINDS / DOCS : add NOSQL features and tags Actions Feature #3448: Provide ODT neutral template for documents on fresh install Actions Feature #3507: Import ISHTAR-operations: add raw_name for persons Actions Feature #3520: OPERATION form: check that all fields available in DB are present in the form Actions Feature #3521: OPERATION sheet: check that all fields available in DB are present in the sheet Actions Feature #3522: FILE form: check that all fields available in DB are present in the form Actions Feature #3523: CONTEXT RECORD form: check that all fields available in DB are present in the form Actions Feature #3524: FINDS form: check that all fields available in DB are present in the form Actions Feature #3525: TREATMENT form: check that all fields available in DB are present in the form Actions Feature #3526: TREATMENT REQUEST form: check that all fields available in DB are present in the form Actions Feature #3527: WAREHOUSE form: check that all fields available in DB are present in the form Actions Feature #3528: OPERATION > ADMINISTRATIVE ACT form: check that all fields available in DB are present in the form Actions Feature #3529: OPERATION > SOURCE form: check that all fields available in DB are present in the form Actions Feature #3530: CONTEXT RECORD > SOURCE form: check that all fields available in DB are present in the form Actions Feature #3531: FINDS > SOURCE form: check that all fields available in DB are present in the form Actions Feature #3532: TREATMENT REQUEST > SOURCE form: check that all fields available in DB are present in the form Actions Feature #3533: TREATMENT REQUEST > ADMINISTRATIVE ACT form: check that all fields available in DB are present in the form Actions Feature #3534: TREATMENT > ADMINISTRATIVE ACT form: check that all fields available in DB are present in the form Actions Feature #3535: TREATMENT > SOURCE form: check that all fields available in DB are present in the form Actions Feature #3536: CONTAINER form: check that all fields available in DB are present in the form Actions Feature #3537: FILE > ADMINISTRATIVE ACT form: check that all fields available in DB are present in the form Actions Feature #3538: FILE sheet: check that all fields available in DB are present in the sheet Actions Feature #3539: CONTEXT RECORD sheet: check that all fields available in DB are present in the sheet Actions Feature #3540: FINDS sheet: check that all fields available in DB are present in the sheet Actions Feature #3541: TREATMENT sheet: check that all fields available in DB are present in the sheet Actions Feature #3542: TREATMENT REQUEST sheet: check that all fields available in DB are present in the sheet Actions Feature #3543: WAREHOUSE sheet: check that all fields available in DB are present in the sheet Actions Feature #3544: OPERATION > ADMINISTRATIVE ACT sheet: check that all fields available in DB are present in the sheet Actions Feature #3545: OPERATION > SOURCE sheet: check that all fields available in DB are present in the sheet Actions Feature #3546: CONTEXT RECORD > SOURCE sheet: check that all fields available in DB are present in the sheet Actions Feature #3547: FINDS > SOURCE sheet: check that all fields available in DB are present in the sheet Actions Feature #3548: TREATMENT > SOURCE sheet: check that all fields available in DB are present in the sheet Actions Feature #3549: TREATMENT REQUEST > SOURCE sheet: check that all fields available in DB are present in the sheet Actions Feature #3550: TREATMENT REQUEST > ADMINISTRATIVE ACT sheet: check that all fields available in DB are present in the sheet Actions Feature #3551: TREATMENT > ADMINISTRATIVE ACT sheet: check that all fields available in DB are present in the sheet Actions Feature #3552: FILE > ADMINISTRATIVE ACT sheet: check that all fields available in DB are present in the sheet Actions Feature #3553: CONTAINER sheet: check that all fields available in DB are present in the sheet Actions Feature #3601: Migration to Python 3 Actions Feature #3629: Importers configuration: add explicit "model that can accept new items" Actions Feature #3648: Ishtar should handle complex treatments Actions Feature #3653: Register automatically models for export Actions Feature #3657: CONTEXT RECORD search : add some criteria Actions Feature #3659: Use native LibreOffice format for imports (exports?) Actions Feature #3667: A better UI for smartphones Actions Feature #3669: Lists should provide thumbnails, when image is present Actions Feature #3743: Connections tracking, reports and statistics Actions Feature #3744: FINDS : we must manage the ownership for FINDS Actions Feature #3758: FIND wizard : Description should be after Type Actions Feature #3865: Some typologies lack examples; we should provide them Actions Feature #3879: WAREHOUSE : can have an image Actions Feature #3933: Document templates: access to JSON field Actions Feature #3935: Creation of virtual operation from site with many operations Actions Feature #3951: Use a work queue for imports Actions Feature #4089: Manage JSON fields in wizards Actions Feature #4107: Manage images like any document Actions Feature #4180: Manage complex searches on the search field : open search, multi criteria, etc. Actions Feature #4244: Sheets: "created by" fields Actions Feature #4302: Form: possibility of adding subsections title for JSON fields as it is possible in sheets Actions Feature #4307: Allow deactivation of "auto-pin" and of "pin menu" in the profile Actions Feature #4308: Pin on the search bar Actions Feature #4319: Finds: add the possibility to duplicate an item's sheet (and data) Actions Feature #4333: ADMIN: add a "parent" column in the alteration types' table Actions Feature #4344: Add linked items in the small info panel of images Actions Feature #4405: Criteria search, SITES, OPERATIONS & CONTEXT RECORD & DOCUMENTS & CONTAINERS : lack of "Has an image?" criteria in advanced search Actions Feature #4450: SITE : needs for a simple button to add an OPERATION linked to a site Actions
3.0 12% 17 issues (2 closed — 15 open) Related issues Bug #4583: DOCUMENTS FORM : image field displayed on creation, not for modification Actions Bug #4855: Finds search: gallery: pagination problem (bis) Actions Bug #4866: Pinned search overloads alerts Actions Bug #4921: Basket search results: the arrow function to switch from one basket to the other does not work Actions Bug #4923: Bad session initialisation when creating a treatment (at least for treatment n -> 1) Actions Bug #4924: Map on find sheet: the map is not displayed when several base finds, except for the first one Actions Bug #4928: The id regeneration action doesn't get the job done Actions Bug #4947: Administrative act: the signature date is mandatory ; it should'nt Actions Bug #4949: Search: bug with accented capital letters Actions Bug #5167: Container sheet: bug when no main image has been designated Actions Bug #5170: Basket list: fix sort by owner Actions Feature #4597: Sites search: the free search should returns only the corresponding sites, not all the ones that are linked to them by a common operation Actions Feature #4943: Admin, importers - columns: add the possibility to sort by target Actions Feature #4956: Admin, types tables: for all hierarchical type lists, add a colum for parent Actions Feature #4961: Operation sheet improvement Actions
future 21% 52 issues (10 closed — 42 open) Related issues Bug #2132: ACTS/Documents : add filter on type of documents Actions Bug #2879: IMPORTS : detecting duplications Actions Bug #3355: FILES : some duplicates in FILES index Actions Bug #3442: DB: Town shouldn't be linked with an area Actions Bug #3443: DB: An operation should be able to have several head scientists (at least research operations) Actions Bug #3466: OPE / parcels add : parsing for parcels with letter not ok Actions Bug #3502: Error deadlock detected in DB with silent error in UI Actions Bug #3505: DB: Lexical problem with element "surname" for persons Actions Bug #3557: Shortcut menu: a pined find is not updated when a treatment is done Actions Bug #4907: Modification form: improve the recapitulation before the last validation Actions Feature #53: Send email to administrators after a new registration Actions Feature #154: OPE CREATION and MODIF / Owner managment Actions Feature #437: Context record and finds creation / No find can be linked to a negative context record Actions Feature #639: Add BOM when using utf8 Actions Feature #2076: DASHBOARD : graphs for OPE Actions Feature #2688: Simples DB stats : we should provide somewhere simple stats of DB's records Actions Feature #2690: PARCELS ADD/MODIF (in OPE) : Parcels could have an owner and a short descriptive field Actions Feature #2794: FINDS : Thesaurus for Object Type Actions Feature #2834: IMPORTS : importing previously recorded data Actions Feature #2888: FINDS / Search : search in many operations Actions Feature #2991: [MODULE SEDIMENT] : A sediment module should provide a panel for UE with detailled descriptions tools Actions Feature #3063: Search panels : with keyboard, "ENTER" = "Search" Actions Feature #3064: EXPORT : add a feature to export and import without loss Actions Feature #3130: FINDS managment : add documents (odt) from template Actions Feature #3324: INSTALL - choose between a list of downloadable fixtures Actions Feature #3354: Importers should have sheetfiles Actions Feature #3433: Ishtar Logo / change by Django admin Actions Feature #3436: CONTEXT RECORD : relatins could be define with a CONTEXTE record from another OPE Actions Feature #3457: Magical datings : CONTEXT RECORD and OPE should gain dating from relations with objetcs (CONTEXT RECORD or FINDS) Actions Feature #3463: DASHBOARD : should be in Ishtar-core Actions Feature #3499: Wizard: optimize saving - do not call update many times Actions Feature #3554: ISHTAR CONFIDENTIAL : some records could be confidential Actions Feature #3582: FINDS : should have an index related to CONTEXT RECORD Actions Feature #3617: GIS module: add Zsup value for FINDS Actions Feature #3630: ORGANIZATION : could have fax number and website Actions Feature #3668: ISHTAR API : ISHTAR should provide an API Actions Feature #4481: Importer types: add a new column "Comment" Actions Feature #4620: Baskets linked with a treatment or a treatment file should be shared with everyone Actions Feature #4673: CONTAINER : sheet file should give additional info Actions Feature #4912: New field "creation date" needed Actions Feature #4915: Admin interface: add a bulk update to disable items Actions Feature #4916: Add a new possibility between available and not available: available for search Actions