Postponing an error across more than one stage

Question

The Komba translation team postponed a error under quotations at the end of stage one and the same error recurred then in stage 2. The error is not a normal error and appears to be a bug in Paratext. I will address the particulars of this bug in another post - that’s not the point of this question. Now we should be in stage 3 but we cannot close stage 2, and we cannot postpone the error. Presumably once a check is postponed from stage one to two, it cannot be postponed again to stage 3, unless we reopen stage one and postpone that check until stage 3. That is not ideal. So I think this might be another bug or a problem in the logic of the checks, such that if you postpone errors in stage one, you cannot postpone the errors again and then can never move onto stage 3. Is this a bug or am I misunderstanding something?

较早的帖子 - 以原始语言显示

Answer 1

I agree. This behavior is a bug. The process chart should be a Guide, not a prison. We’ve been tripped up by this as well.
Not all errors or incomplete tasks are actually show-stoppers. Many are bookkeeping tasks. These we often need to postpone simply because of time constraints. (And some are not errors but PT8 wrongly flags them as errors. These we simply postpone to the very last stage.)
There doesn’t appear to be an admin override other than postponing, and that is only allowed once. Please make this not a blocking rule.

较早的帖子 - 以原始语言显示

Answer 2

Yes, I agree! Checks should be able to be postponed any number of times. This also happens because new issues are introduced at a later stage, but now we’re supposed to be working in the next stage but these issues are hanging in the previously otherwise completed stage. It’s not time to go back and deal with the issues right now, but this bug in the program is making us do just that.

较早的帖子 - 以原始语言显示

Answer 3

I don’t see how your workaround of going back to Stage 1 and (re-)postponing until Stage 3 is even possible. I see no way to do that, although I vaguely remember figuring this workaround out myself last year. I see no way to do it now.

较早的帖子 - 以原始语言显示

Answer 4

I strongly agree that checks should be able to be postponed any number of times. There are numerous times when the user responsible for working through a particular check is not available when the team is ready to move on. This has been particularly troublesome for books that were in process before PT8’s Plan was implemented. We need to check/report progress on those books but the Progress Report will not indicate the true progress because of some “small” glitch that can not be fixed until later.

较早的帖子 - 以原始语言显示