why my calculated value script run even when the change is not triggered?
Hi, Someone who may concern,
We found a very strange issue lately.
We have 2 projects, running the same calculate value script. The purpose is that when status is changed to close, then the date will be recorded
I have configured the Dependencies as "Status" for both projects, i.e. only when user change status to close, this script will run.
dojo.provide("client.valueProvider.currentCloseDate");
dojo.require("dojo.date.stamp");
dojo.require("com.ibm.team.workitem.api.common.WorkItemAttributes");
(function() {
var WorkItemAttributes = com.ibm.team.workitem.api.common.WorkItemAttributes;
dojo.declare("client.valueProvider.currentCloseDate", null, {
getValue: function(attribute, workItem, configuration) {
var now = dojo.date.stamp.toISOString(new Date(), {milliseconds:true, zulu:true});
var state = workItem.getValue(WorkItemAttributes.STATE);
var myOldValue = workItem.getValue(attribute);
if (state ===='xxx.state.close') {
return now;
}
else
return myOldValue;
}
});
}) ();
However, on the old project, it can work properly.
But the new project, which is created with the same script, it cannot work properly:
as long as I refresh the page for a work item with status as "Close", the close date will be updated to current time. It seems my script run without trigger of status change.
However, I also noticed for the same project, defect can not work, but task can work. both of them share the same attribute for the close date.
Then I added break point in my script, and refresh the page, the break point can not be reached.
And I tried to add a console.log in the script to make sure whether the script run, but console did not show anything.
It seems this script run before tracing ability is enabled.
Because as long as I remove the script, the correct close date can be shown properly. So I am 100% sure there are something wrong for running this script.
I am wondering any configuration may cause such issue?
Thanks!
Best Regards,
Jane Zhou
3 answers
I think the problem here is your assumption that you can detect a state change in a JavaScript attribute customization (calculated value?) for all I know you can't. The only ways to be able to do so would be the ability to access the old state which you don't have, access to the action which you don't have except in conditions or storing the old state in a hidden attribute, which I don't see.
I have summarized my experience and common misconceptions here: https://rsjazz.wordpress.com/2016/07/15/rtc-process-customization-what-you-can-and-cannot-do/
Hi Ralph,
Thanks for your reply!
The part you did not see is configured in Eclipse client to add Dependencies to the attribute close_date with calculated value. The purpose is that only when dependent attribute change then related calculated value script will run.
For my case, the calculated value is attached to attribute close_date, and dependent attribute is Status.
The same attribute close_date is shared between type of Defect and Task. However, it can work for task, but can not work for defect.
So, if my script can not work, they should not work for both cases. why it can work for task, but not for defect?
And in fact, I noticed the history did not show the close_date is updated to current time when I refresh the work item page. i.e. it only displays that way, but in database, it still record the original close_date which triggered by state change.
Thanks!
Best Regards,
Jane Zhou
You just made things very confusing.
Refreshing a page does not change anything of the work item. If you see that an attribute has an incorrect value, it is a "display" issue.
The calculated value provider will be executed at different timings, and you should understand when it will be executed.
https://jazz.net/wiki/bin/view/Main/AttributeCustomization#Script_based_calculated_values
As far as I know, reusing an attribute does not share the provider configurations.
And finally, different types of work items are likely using different workflows, hence the state ID can be different. Make sure that you specify the correct state ID in your code.
Comments
