2.0 - maintenance 57% 14 issues (8 closed — 6 open) Related issues Evolution #3763: Debian package for v2 (stretch) Actions Evolution #3950: Sites - Shortcut menu availability Actions Evolution #3963: IMPORTS : if there is an error the link to the CSV file should be in bold red Actions
2.1 23% 129 issues (29 closed — 100 open) Related issues Evolution #55: Add a profile page Actions Evolution #3077: OPE / CONTEXT RECORD / FINDS / DOCS : add NOSQL features and tags Actions Evolution #3448: Provide ODT neutral template for documents on fresh install Actions Evolution #3507: Import ISHTAR-operations: add raw_name for persons Actions Evolution #3520: OPERATION form: check that all fields available in DB are present in the form Actions Evolution #3521: OPERATION sheet: check that all fields available in DB are present in the sheet Actions Evolution #3522: FILE form: check that all fields available in DB are present in the form Actions Evolution #3523: CONTEXT RECORD form: check that all fields available in DB are present in the form Actions Evolution #3524: FINDS form: check that all fields available in DB are present in the form Actions Evolution #3525: TREATMENT form: check that all fields available in DB are present in the form Actions Evolution #3526: TREATMENT REQUEST form: check that all fields available in DB are present in the form Actions Evolution #3527: WAREHOUSE form: check that all fields available in DB are present in the form Actions Evolution #3528: OPERATION > ADMINISTRATIVE ACT form: check that all fields available in DB are present in the form Actions Evolution #3529: OPERATION > SOURCE form: check that all fields available in DB are present in the form Actions Evolution #3530: CONTEXT RECORD > SOURCE form: check that all fields available in DB are present in the form Actions Evolution #3531: FINDS > SOURCE form: check that all fields available in DB are present in the form Actions Evolution #3532: TREATMENT REQUEST > SOURCE form: check that all fields available in DB are present in the form Actions Evolution #3533: TREATMENT REQUEST > ADMINISTRATIVE ACT form: check that all fields available in DB are present in the form Actions Evolution #3534: TREATMENT > ADMINISTRATIVE ACT form: check that all fields available in DB are present in the form Actions Evolution #3535: TREATMENT > SOURCE form: check that all fields available in DB are present in the form Actions Evolution #3536: CONTAINER form: check that all fields available in DB are present in the form Actions Evolution #3537: FILE > ADMINISTRATIVE ACT form: check that all fields available in DB are present in the form Actions Evolution #3538: FILE sheet: check that all fields available in DB are present in the sheet Actions Evolution #3539: CONTEXT RECORD sheet: check that all fields available in DB are present in the sheet Actions Evolution #3540: FINDS sheet: check that all fields available in DB are present in the sheet Actions Evolution #3541: TREATMENT sheet: check that all fields available in DB are present in the sheet Actions Evolution #3542: TREATMENT REQUEST sheet: check that all fields available in DB are present in the sheet Actions Evolution #3543: WAREHOUSE sheet: check that all fields available in DB are present in the sheet Actions Evolution #3544: OPERATION > ADMINISTRATIVE ACT sheet: check that all fields available in DB are present in the sheet Actions Evolution #3545: OPERATION > SOURCE sheet: check that all fields available in DB are present in the sheet Actions Evolution #3546: CONTEXT RECORD > SOURCE sheet: check that all fields available in DB are present in the sheet Actions Evolution #3547: FINDS > SOURCE sheet: check that all fields available in DB are present in the sheet Actions Evolution #3548: TREATMENT > SOURCE sheet: check that all fields available in DB are present in the sheet Actions Evolution #3549: TREATMENT REQUEST > SOURCE sheet: check that all fields available in DB are present in the sheet Actions Evolution #3550: TREATMENT REQUEST > ADMINISTRATIVE ACT sheet: check that all fields available in DB are present in the sheet Actions Evolution #3551: TREATMENT > ADMINISTRATIVE ACT sheet: check that all fields available in DB are present in the sheet Actions Evolution #3552: FILE > ADMINISTRATIVE ACT sheet: check that all fields available in DB are present in the sheet Actions Evolution #3553: CONTAINER sheet: check that all fields available in DB are present in the sheet Actions Evolution #3601: Migration to Python 3 Actions Evolution #3629: Importers configuration: add explicit "model that can accept new items" Actions Evolution #3648: Ishtar should handle complex treatments Actions Evolution #3653: Register automatically models for export Actions Evolution #3657: CONTEXT RECORD search : add some criteria Actions Evolution #3659: Use native LibreOffice format for imports (exports?) Actions Evolution #3667: A better UI for smartphones Actions Evolution #3669: Lists should provide thumbnails, when image is present Actions Evolution #3740: Randomly diplayed image should include images from DOCs thumbnails Actions Evolution #3743: Connections tracking, reports and statistics Actions Evolution #3744: FINDS : we must manage the ownership for FINDS Actions Evolution #3758: FIND wizard : Description should be after Type Actions Evolution #3865: Some typologies lack examples; we should provide them Actions Evolution #3879: WAREHOUSE : can have an image Actions Evolution #3933: Document templates: access to JSON field Actions Evolution #3935: Creation of virtual operation from site with many operations Actions Evolution #3951: Use a work queue for imports Actions Evolution #3962: Make parcel not mandatory for context record (direct link to the operation) Actions Evolution #3975: Step by step imports Actions Evolution #4039: Finds: discovery date: add a new TAQ field Actions Evolution #4042: Create a basket from search results Actions Evolution #4046: Change permissions to use type of profile and not type of user Actions Evolution #4048: Manage a new type of operation (beside Preventive/Research) for court-ordered seizure Actions Evolution #4060: Add "areas" to manage own item permissions Actions Evolution #4076: Wizards: simple management of many to many images Actions Evolution #4089: Manage JSON fields in wizards Actions Evolution #4107: Manage images like any document Actions Evolution #4178: Use pandoc to generate ODT Actions Evolution #4180: Manage complex searches on the search field : open search, multi criteria, etc. Actions Evolution #4234: JSON fields, admin table: new columns needed Actions Evolution #4235: JSON boolean fields not displayed correctly Actions Evolution #4244: Sheets: "created by" fields Actions Evolution #4248: Add display of attached areas after towns in all sheets Actions Evolution #4302: Form: possibility of adding subsections title for JSON fields as it is possible in sheets Actions Evolution #4307: Allow deactivation of "auto-pin" and of "pin menu" in the profile Actions Evolution #4308: Pin on the search bar Actions Evolution #4319: Finds: add the possibility to duplicate an item's sheet (and data) Actions Evolution #4333: ADMIN: add a "parent" column in the alteration types' table Actions Evolution #4344: Add linked items in the small info panel of images Actions Evolution #4405: Criteria search, SITES, OPERATIONS & CONTEXT RECORD & DOCUMENTS & CONTAINERS : lack of "Has an image?" criteria in advanced search Actions Evolution #4450: SITE : needs for a simple button to add an OPERATION linked to a site Actions Evolution #4540: Treatment request sheet: add links to the associated administrative act and basket sheets Actions
3.0 13% 15 issues (2 closed — 13 open) Related issues Evolution #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 Evolution #4943: Admin, importers - columns: add the possibility to sort by target Actions Evolution #4956: Admin, types tables: for all hierarchical type lists, add a colum for parent Actions Evolution #4961: Operation sheet improvement Actions
beta 93% 14 issues (13 closed — 1 open) Related issues Evolution #4939: Container search: add quick actions (for group modifications) Actions Evolution #4995: Admin, containers types: add columns in the search results display Actions Evolution #4997: Packaging quick action: improve display of the modification choice Actions Evolution #4999: New action needed: attach a document to an administrative act Actions Evolution #5000: New action needed: attach a document to another document (metadata) Actions
future 12% 52 issues (5 closed — 47 open) Related issues Evolution #53: Send email to administrators after a new registration Actions Evolution #154: OPE CREATION and MODIF / Owner managment Actions Evolution #302: Manage Treatments Actions Evolution #303: Warehouse management Actions Evolution #437: Context record and finds creation / No find can be linked to a negative context record Actions Evolution #483: FIND research / Search by warehouse Actions Evolution #498: TREATMENTS/SOURCES management Actions Evolution #499: TREATMENTS/Manage many to one treatment Actions Evolution #514: FIND / Manage defaut item Actions Evolution #633: OPE sheet file / Should provide man-days Actions Evolution #639: Add BOM when using utf8 Actions Evolution #640: Share informations between Ishtar instances Actions Evolution #2076: DASHBOARD : graphs for OPE Actions Evolution #2688: Simples DB stats : we should provide somewhere simple stats of DB's records Actions Evolution #2690: PARCELS ADD/MODIF (in OPE) : Parcels could have an owner and a short descriptive field Actions Evolution #2794: FINDS : Thesaurus for Object Type Actions Evolution #2834: IMPORTS : importing previously recorded data Actions Evolution #2888: FINDS / Search : search in many operations Actions Evolution #2991: [MODULE SEDIMENT] : A sediment module should provide a panel for UE with detailled descriptions tools Actions Evolution #3063: Search panels : with keyboard, "ENTER" = "Search" Actions Evolution #3064: EXPORT : add a feature to export and import without loss Actions Evolution #3130: FINDS managment : add documents (odt) from template Actions Evolution #3324: INSTALL - choose between a list of downloadable fixtures Actions Evolution #3354: Importers should have sheetfiles Actions Evolution #3433: Ishtar Logo / change by Django admin Actions Evolution #3436: CONTEXT RECORD : relatins could be define with a CONTEXTE record from another OPE Actions Evolution #3457: Magical datings : CONTEXT RECORD and OPE should gain dating from relations with objetcs (CONTEXT RECORD or FINDS) Actions Evolution #3463: DASHBOARD : should be in Ishtar-core Actions Evolution #3499: Wizard: optimize saving - do not call update many times Actions Evolution #3554: ISHTAR CONFIDENTIAL : some records could be confidential Actions Evolution #3582: FINDS : should have an index related to CONTEXT RECORD Actions Evolution #3617: GIS module: add Zsup value for FINDS Actions Evolution #3630: ORGANIZATION : could have fax number and website Actions Evolution #3668: ISHTAR API : ISHTAR should provide an API Actions Evolution #4481: Importer types: add a new column "Comment" Actions Evolution #4620: Baskets linked with a treatment or a treatment file should be shared with everyone Actions Evolution #4673: CONTAINER : sheet file should give additional info Actions Evolution #4912: New field "creation date" needed Actions Evolution #4915: Admin interface: add a bulk update to disable items Actions Evolution #4916: Add a new possibility between available and not available: available for search Actions