Actions
User story #1362
closed[Specs] Define dependencies between actions for historisation
Status:
Rejected
Priority:
N/A
Assignee:
-
Category:
Web - Maintenance
Target version:
-
Pull Request:
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:
Description
We need to discuss (FAR, NCH and JCL) which actions depend on which others, and what and how to store in our history of actions.
Updated by François ARMAND almost 13 years ago
- Target version changed from 13 to 14
Updated by Jonathan CLARKE over 12 years ago
- Target version changed from 14 to 16
Updated by Jonathan CLARKE over 12 years ago
- Target version changed from 16 to 10
Updated by François ARMAND over 12 years ago
- Category changed from Web - UI & UX to 32
- Assignee deleted (
Jonathan CLARKE) - Priority changed from 1 to N/A
- Target version changed from 10 to 18
That issue does not seems to be still up to the reality, because since the time it was open, a lot was done in "event log", some part being mostly alike what was describe here.
I move that to 2.4 ideas for now.
Updated by François ARMAND over 12 years ago
- Target version changed from 18 to 24
Updated by Jonathan CLARKE over 11 years ago
- Target version changed from 24 to 18
Updated by François ARMAND over 11 years ago
- Status changed from 2 to Discussion
Comment #5 is event more true, and so that ticket shoud be rejected.
Updated by Jonathan CLARKE over 11 years ago
- Status changed from Discussion to Rejected
Prehistoric ticket, rejecting - this has been handled via event logs (see François comment in #5)
Actions