Task promotion has implicit warning checks for the following conditions:
- No content changes made in the task.
- Classification has been run in the task.
- Classification was started but either failed to complete or has not completed.
- Classification is current.
- Classification has no results to accept.
- Classification results have been accepted.
- Review has been completed.
If no content has been changed on the task when promotion is initiated, a Promote Task pop-up notification states the there are no changes to promote. Press Return to Task
(or press the X
in the upper right corner) to close the pop-up.
If content changes have been made but any of the other conditions are not yet satisfied when promotion is initiated, a Promote Task pop-up notification shows their statuses, with action options to cancel the promotion, or to continue if task changes are considered sufficiently safe to update the project level content without satisfying these conditions.
Press Return to Task
(or press the X
in the upper right corner) to close the pop-up and cancel the promotion without changing project content or the task status.
Press Promote Anyway
to continue promotion.
Note |
---|
title | Promoting tasks despite with warnings |
---|
|
Pressing Promote Anyway is is tacit acceptance of any warning statuses, with implied responsibility for by-passing these safeguards and the consequent unclassified and/or unreviewed content changes that will be promoted from the task to the project level. Promoting unclassified content changes is a quality assurance risk that can be avoided relatively easily, since it typically takes less than ten minutes to run classification (if only to confirm no results). However there are occasions when it is clear that inferred classification results won't change, such as a description-only content change, in which case this option may save a little time if neededbe acceptable. By-passing review is another scenario where this option can save timemay also be acceptable under particular circumstances, for instance if the author is also implicitly the reviewer or perhaps the project manager / project lead. Note that this scenario won't be feasible if the task is made into a Complex task and Review Completed is also set can be prevented by setting the task as Complex and also having Review Completed set as a mandatory task-level SAC requirement within its parent project configuration, since promotion can't task promotion in this case will not be enabled without a completed review in this case. |