Our acceptance dashboard counts another housing every time a successful retry arrives, although the physical housing identity is unchanged; how should the developer show one current disposition while keeping every failed and repeated attempt available?
How should our FR10 housing report count a reviewed retry?
DominicBowen · 2026年2月28日 19:50 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
7 条回复
回复 DominicBowen
Make the housing the parent record and retain attempts underneath it. Count current authorised accepted dispositions, not success events. Test a failed attempt, reviewed retry, duplicate result and restart against the same housing identity.
25分回复 DominicBowen
Who decides that a successful retry releases the housing, Dominic, rather than leaving it held for review?
25分Quality owns release, Hassan; the existing report treats inspection success as release without consulting that disposition, so we have found a second reason its accepted total is wrong
16分回复 DominicBowen
Then include a successful result with a continuing hold in the test. Keep it out of the accepted count and show the remaining decision plainly. Otherwise fixing duplicates still leaves the report sending the wrong message.
6分Offline cases now retain all attempts, keep the successful held housing out of the accepted total and count the released one once after duplicate delivery and restart; actual workstation comparison still to do
13分回复 DominicBowen
Will whoever covers the station see that held housing in the remaining work, even when they're looking at the accepted total?
21分回复 DominicBowen
And compare the exported report at the workstation as well. It may build its total through another path, so a correct screen doesn't automatically repair what the supervisor receives.
25分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .