Content
View differences
Updated by Judith Roth 4 months ago
## **Things that need to be adapted / specified**
<br>
### Views to adapt (replace id with semantic id)
\=> which of these need to be redesigned because the new identifiers take more space? Especially also for mobile web?
\=> should we limit the amount of characters for project identifiers to avoid "broken" layouts? => <mention class="mention" data-id="71627" data-type="work_package" data-text="#71627">#71627</mention>
* [ ] List of work packages
- List itself
- Filter by ID opens picker
* [ ] Work package show view
- Above description
- Relations Tab
- Git Snippets for GitHub and GitLab
* [ ] Work package split screen view
* [ ] Boards
* [ ] Work package links in CKEditor (also the selector dropdown when searching)
* [ ] Work package links in BlockNote
* [ ] Activity lists (per project, global, per person)
* [ ] Roadmap
* [ ] Gantt charts (is this a separate view or the same as the list of work packages?)
* [ ] Team Planners
* [ ] Backlogs???
* [ ] My page (are the widgets there separate views or the same as the list of work packages?)
* [ ] ???
### Other things
* [ ] Change the project's identifier dialog to enforce stricter validations if the semantic ids are used (length is enforced to be max 10 characters - if we want to allow more later on we can still add a separete setting for project identifier length later on like jira has it) => important
* [ ] When a new project is created and semanic IDs are used for that instance, we need to create a short enough project identifier for it automatically
* [ ] Search + Filters!!! (search for semantic work package IDs, search for project identifiers) => Important
* [ ] Filter / Search <project identifier> > / < <id> will we do later, not now (therefore search for larger, smaller) => Important
* [ ] API (where is information exposed and where do we accept the new sequences as identifiers)
- todo: decide if API routes may contain semantic ids or not - do they support it for project identifiers or not?
* [ ] Mobile App (talk to Marc)
* [ ] Excel syncs???
* [ ] BIM edition - BCF Export and Import
* [ ] Mobile App (=> API, talk to Marc)
* [ ] Github und Gitlab op#<id> in PRs etc. (webhook) / Repository module: Work package referencing
* [ ] PDF export
* [ ] URLs / routes - should accept all valid handles for a work package, therefore id and semantic ids
- in the actual route to a resource you can use both identifiers and semantic ids
- in the query part regular ids should be used instead of semantic ids for more stability unless it's a search term
* [ ] The functionality which moves a work package to another project needs to be adapted to also create the new semantic identifier
* [ ] ??? (please add what is missing)
* [ ] Maybe semantic work package IDs should be the new default when a new instance is created - check with Wieland again if this is stil the plan when we're finished developing
<br>
### Views to adapt (replace id with semantic id)
\=> which of these need to be redesigned because the new identifiers take more space? Especially also for mobile web?
\=> should we limit the amount of characters for project identifiers to avoid "broken" layouts? => <mention class="mention" data-id="71627" data-type="work_package" data-text="#71627">#71627</mention>
* [ ] List of work packages
- List itself
- Filter by ID opens picker
* [ ] Work package show view
- Above description
- Relations Tab
- Git Snippets for GitHub and GitLab
* [ ] Work package split screen view
* [ ] Boards
* [ ] Work package links in CKEditor (also the selector dropdown when searching)
* [ ] Work package links in BlockNote
* [ ] Activity lists (per project, global, per person)
* [ ] Roadmap
* [ ] Gantt charts (is this a separate view or the same as the list of work packages?)
* [ ] Team Planners
* [ ] Backlogs???
* [ ] My page (are the widgets there separate views or the same as the list of work packages?)
* [ ] ???
### Other things
* [ ] Change the project's identifier dialog to enforce stricter validations if the semantic ids are used (length is enforced to be max 10 characters - if we want to allow more later on we can still add a separete setting for project identifier length later on like jira has it) => important
* [ ] When a new project is created and semanic IDs are used for that instance, we need to create a short enough project identifier for it automatically
* [ ] Search + Filters!!! (search for semantic work package IDs, search for project identifiers) => Important
* [ ] Filter / Search <project identifier> > / < <id> will we do later, not now (therefore search for larger, smaller) => Important
* [ ] API (where is information exposed and where do we accept the new sequences as identifiers)
- todo: decide if API routes may contain semantic ids or not - do they support it for project identifiers or not?
* [ ] Mobile App (talk to Marc)
* [ ] Excel syncs???
* [ ] BIM edition - BCF Export and Import
* [ ] Mobile App (=> API, talk to Marc)
* [ ] Github und Gitlab op#<id> in PRs etc. (webhook) / Repository module: Work package referencing
* [ ] PDF export
* [ ] URLs / routes - should accept all valid handles for a work package, therefore id and semantic ids
- in the actual route to a resource you can use both identifiers and semantic ids
- in the query part regular ids should be used instead of semantic ids for more stability unless it's a search term
* [ ] The functionality which moves a work package to another project needs to be adapted to also create the new semantic identifier
* [ ] ??? (please add what is missing)
* [ ] Maybe semantic work package IDs should be the new default when a new instance is created - check with Wieland again if this is stil the plan when we're finished developing