Hello,
hope someone out there may help with a solution/workaround.
The challenge:
I have a project containg two issue types: Task and Improvement:
Task issues of type Task contain ideas for further extented implementation of a software (+1000). These tasks are initially of a status "open" and are categorized via a customfield A, B, C, D with a weighting value of 1 (=low) to 3(=high) giving the potential positive impact to the software.
If the implementation idea shall be implemented the Task will be moved to a status "tobeimplemented"
Additionally there are issues of Type Improvement defined per category A, B, C, D,... with a field counting the weighting values of all implementation ideas in status "tobeimplemented".
I have implemented this as a rule for the issue typ Task being executed for each Task being moved to status "tobeimplmented"
The rule simply picks up the related issue of type improvement and adds the weighting factor of that issue to the custom counter of the related issue of type Improvement based upon its category..
The rule works fine, as long as I move task by Task to the status "tobeimplemnted"
As soon as I do a bulk update and move more than one task to the status "tobeimplmented" it doesn't add to the actual value of the counter field, i.e.
- I do a bulk update of two tasks of category A with weighting factor of 1 each.
- The counter value before execution of the change 100.
- the expected result should be 100 + 1 + 1 = 102
- the rule is executed properl twice,
- the audit log shows, that the counter value to be added by 1 in both cases is 100
It seems to be an transactional issue because two instances of a rule working on the same improvement issue at the sametime.
How may I solve the probelm? Any ideas?
Kind Regards
Johannes
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.