what events to use on lfWatch when simulating a cascading field

[Jay Keck]

I have a case where I have 2 single choice pulldown fields A and B, and I have tied them together using lfhide,lfshow so that A is thae parent element and the value chosen in it determines which options are displayed in field B. It's working pretty well, wworks fine on create screen, but I'm having a problem where if I bring up and edit field B, all possible choices are coming up, so it's ignorning what field A is set to. And then if I select a new value for field B that field kind of locks up, I can no longer click on it and get any list of items to choose from. I've tried different lfWatch combinations and event settings, but I'm still having the trouble. What is the correct way to configure the lfWatches to deal with this case?

Thanks,

Jay

[Jobin Kuruvilla [Adaptavist] · Accepted solution]

The only thing you have to do it to configure the board with Estimation statistic as "Story Points" and then select "Time Tracking" to None.

See https://confluence.atlassian.com/jirasoftwareserver/configuring-estimation-and-tracking-938845319.html

Once you did that, stories will burn down once they reach then right most column in the board, not when it is done per the workflow. Make sure your "done" statuses are mapped to the last column on the board.

[Cédric Compagnon]

Ok so I have done everything already, maybe the chart don't take sub-tasks or task in consideration I guess...

[Jobin Kuruvilla [Adaptavist]]

Sub-tasks - no. Parent tasks - yes. You should see the burndown as long as the Done status is the right most column on the board.

[Mirek]

The burndown chart uses the Estimation Statistic set for your board. It need to be set to Story Points and when you complete a ticket that have some story points set burndown chart will get updated.