|
Anonymous | Login | Signup for a new account | 2024-11-22 10:18 CET |
Main | My View | View Issues | Change Log | Roadmap | Docs |
Viewing Issue Advanced Details [ Jump to Notes ] | [ View Simple ] [ Issue History ] [ Print ] | ||||||
ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||
0000076 | [Oberon Platform] Context Design | feature | always | 2012-08-08 16:07 | 2012-08-08 16:11 | ||
Reporter | administrator | View Status | public | ||||
Assigned To | administrator | ||||||
Priority | normal | Resolution | fixed | Platform | |||
Status | resolved | OS | |||||
Projection | none | OS Version | |||||
ETA | none | Fixed in Version | 3.0 - DB build 0067 | Product Version | 2.6 - DB build 0065 | ||
Target Version | 3.0 - DB build 0067 | Product Build | |||||
Summary | 0000076: Enabling the history trace for a specific event for all stages | ||||||
Description |
Currently, if I need to enable the history trace for a specific event (for example the "edit" event) for all stages in a lifecycle, I have to set the flag for each stage. This operation may require lot of time when you have several stages. There should be a common mask for the lifecycle where we can enable the trace events valid for all stages. |
||||||
Steps To Reproduce | |||||||
Additional Information | |||||||
Tags | No tags attached. | ||||||
Attached Files | |||||||
|
© 2008-2013 Mirko Solazzi | Website
Templates by IceTemplates.com
Please Read: Privacy Policy and Terms of Use |