Details
-
New Feature
-
Resolution: Fixed
-
None
-
Critical
-
Defining and changing field can be high resource usage. Please do it with coordination with the translate5 support team.
-
New feature where custom fields can be defined for a task.
Description
- Custom meta data fields for project and tasks
- Needed for the new client portal
- On system level additional field defineable
- field types
- boolean
- text
- textarea
- picklist (values can be defined)
- field types
- Show up in
- project grid
- task overview
- new client portal project overview (optionally)
- First screen of project wizard (optionally)
- Client portal order/offer form
- Must be exportable also with the "export meta data" button in task overview into Excel
- In system configuration a new tab "custom fields" is added. It contains
- a grid with all added custom fields with the columns
- ID
- Label
- Tooltip
- Type
- "Add" button to add new blank row
- First row of the grid is selected by default
- Right side shows a config panel to configure the currently selected row
- UI-Texts: Grid similar to what we have in the config for editing Okapi instances. Columns
- Language rfc5646 code
- Label text (with max length because of UI)
- Tooltip text
- Type: Selectable
- Boolean
- Text
- Textarea
- Picklist
- If picklist is selected: Additional grid with 2 columns:
- Entry value (editable text field)
- Entry text (non-editable text, that lists the current values; on click it opens a pop-up with a grid analogous to what we have for label)
- If text is selected: Additional text field "Regex for UI validation"
- Mandatory: Checkbox, that defines, if the field is mandatory in project wizard and client portal
- Shown in project wizard: Checkbox
- UI-Texts: Grid similar to what we have in the config for editing Okapi instances. Columns
- Role-dependent visibility of all meta fields of tasks (be it custom or not custom)
- roles define, in what view a field is visible (client portal, task overview)
- a grid with all added custom fields with the columns
-
-
- for custom fields this is setable via UI (implementation hint: respect that editor role is set automatically, if PM role is set, etc.)
- for non-custom fields this is only setable in DB ACL config
- A simple mechanism that allows to define the order of the fields in project wizard
- All custom fields will be placed
- below the standard fields in client offer/order form and first screen of project wizard
- at the right side of the standard fields in tabular views (grids)
-
- Projects in client portal and projects and tasks in standard translate5 are filterable and sortable by the custom fields
Attachments
Issue Links
- blocks
-
- Open
-
- Open
-
- Selected for dev
- is blocked by
-
- Done
- mentioned in
-
Page Loading...
-
-
-
-
-
-
-