Content
Updated by Sven Kunze 7 months ago
## Situation
Projekt managers create chains of work-packages that are connected via the "follows" relationship. That is implemented via a template so that people can just copy/paste and close all the superfluous tasks from the chain. Unfortunately, the follow relationship is still active an prevents changing start and end dates of open tasks.
This happens because users forget to set the end date when they close/reject a work-package.
People are used to set the status via the status field. So, when they close the ticket, auxilliary information should be updated without changing the known workflow or re-learning the interface.
## User Story
**As** a user
**I don't want to** manually set the end date when I close a work-package
**so that** I subsequent work-packages (via the "follows" relationship) can be changed without accidental errors.
**Acceptance criteria**
* When Ticket status set to a closed Status ("Closed", "Rejected"), set the close => end date by the following logic
* if start-date & due-date are set, then
* set due-date to = today
* unconditionally
* set start-date to today
* if the start-date was set to a (+ start date after today
* otherwise leave alone
* if only start-date or only due-date is set, then
* set due-date to today
* unconditionally
* set start-date to today
* if the start-date was set to a date after today
* otherwise leave alone
* if no date is set, then
* leave dates alone
* the main goal is to reduce problems with superfluous relations
* by either having dates set to NULL
* or by having dates set to the past, so people can plan the future
I don't see how this can be done using actions right now for three reasons:
* very complex logic that the configuration UI cannot handle
* we cannot unset dates via the actions configuration UI
* maybe modifying dates is not the right tool for the problem of deactivating follow relationships when task become irrelevant for planning possibly as well)
Projekt managers create chains of work-packages that are connected via the "follows" relationship. That is implemented via a template so that people can just copy/paste and close all the superfluous tasks from the chain. Unfortunately, the follow relationship is still active an prevents changing start and end dates of open tasks.
This happens because users forget to set the end date when they close/reject a work-package.
People are used to set the status via the status field. So, when they close the ticket, auxilliary information should be updated without changing the known workflow or re-learning the interface.
## User Story
**As** a user
**I don't want to** manually set the end date when I close a work-package
**so that** I subsequent work-packages (via the "follows" relationship) can be changed without accidental errors.
**Acceptance criteria**
* When
* if start-date & due-date are set, then
* set due-date to
* unconditionally
* set start-date to today
* if the start-date was set to a
* otherwise leave alone
* if only start-date or only due-date is set, then
* set due-date to today
* unconditionally
* set start-date to today
* if the start-date was set to a date after today
* otherwise leave alone
* if no date is set, then
* leave dates alone
* the main goal is to reduce problems with superfluous relations
* by either having dates set to NULL
* or by having dates set to the past, so people can plan the future
I don't see how this can be done using actions right now for three reasons:
* very complex logic that the configuration UI cannot handle
* we cannot unset dates via the actions configuration UI
* maybe modifying dates is not the right tool for the problem of deactivating follow relationships when task become irrelevant for planning