|
OBEROn - Bug Trace - Oberon Platform
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 76 | Context Design | feature | always | 2012-08-08 16:07 | 2012-08-08 16:11 |
|
|
|||||
| Reporter: | administrator | Platform: | |||
| Assigned To: | administrator | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | resolved | Product Version: | 2.6 - DB build 0065 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 3.0 - DB build 0067 | ||
|
|
|||||
| 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: | |||||
| Relationships | |||||
| Attached Files: | |||||
|
|
|||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2012-08-08 16:07 | administrator | New Issue | |||
| 2012-08-08 16:07 | administrator | Fixed in Version | => 2.7 build 0066 | ||
| 2012-08-08 16:07 | administrator | Target Version | => 2.7 build 0066 | ||
| 2012-08-08 16:11 | administrator | Note Added: 0000146 | |||
| 2012-08-08 16:11 | administrator | Status | new => resolved | ||
| 2012-08-08 16:11 | administrator | Resolution | open => fixed | ||
| 2012-08-08 16:11 | administrator | Assigned To | => administrator | ||
| 2012-08-08 16:12 | administrator | Note Edited: 0000146 | |||
| Notes | |||||
|
|
|||||
|
|
||||