- Status Researching
- Percent Complete
- Task Type Feature Request
- Category Backend/Core
- Assigned To No-one
- Operating System All
- Severity Low
- Priority Very Low
- Reported Version 1.0-beta
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
FS#2190 - enable move of a closed clask to other project without reopening it
Problem: By replacing just the project_id of the closed task it is possible the task then has invalid field values within the target project.
Possible scenarios:
- Ignore invalid values within the target project
- Pro: Easy to do, an immidiatly revert back to the old project would “heal” the task properties.
- Contra: may effect accuracy and reliability of other parts like searching, listing, statistic calculations
- Silent change task field values to valid field values of the target project if necessary
- Pro: relative easy to do
- Contra: a bit loss of information, little side effects
- allow user to modify the fields that must be changed so that every field of the task has valid values within the target project
- Pro: accuracy
- Contra: a bit loss of information(fallback to default values) if there are no similiar field values selectable within the project
- allow user to modify the fields, fields or field select values that do not exists in target project will be automatically created.
- Pro: accuracy
- Contra: target project may be cluttered with too many fields/field values
- ???
Loading...
Available keyboard shortcuts
- Alt + ⇧ Shift + l Login Dialog / Logout
- Alt + ⇧ Shift + a Add new task
- Alt + ⇧ Shift + m My searches
- Alt + ⇧ Shift + t focus taskid search
Tasklist
- o open selected task
- j move cursor down
- k move cursor up
Task Details
- n Next task
- p Previous task
- Alt + ⇧ Shift + e ↵ Enter Edit this task
- Alt + ⇧ Shift + w watch task
- Alt + ⇧ Shift + y Close Task
Task Editing
- Alt + ⇧ Shift + s save task