[MGNLMIGRATION-178] ReportingService: Add method to check whether the task/script result has been already set Created: 03/Dec/12 Updated: 04/Dec/12 Resolved: 03/Dec/12 |
|
| Status: | Closed |
| Project: | Migration 4.4 to 4.5 (closed) |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.2 |
| Type: | New Feature | Priority: | Neutral |
| Reporter: | Jozef Chocholacek | Assignee: | Jozef Chocholacek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Date of First Response: |
| Description |
|
When subtasks are processed, the result is sometimes set within the subtask, so the post-process setting is unwanted. Thus we need a method to check whether the task (or script) result has been already set. |
| Comments |
| Comment by Jozef Chocholacek [ 03/Dec/12 ] |
|
Implemented, tested, committed, pushed. |
| Comment by Jan Haderka [ 03/Dec/12 ] |
Surely you can think of better description |
| Comment by Jozef Chocholacek [ 03/Dec/12 ] |
|
Sorry for the previous imprecise description, it'd been created in a hurry. |