Conversation
What was broken Task challenge setup in the Work app displayed a Copilot Fee field, allowing project managers to bundle a copilot payment with the task. Root cause The challenge editor rendered the copilot fee input for every billable challenge without considering the resolved task challenge state. What was changed - Hide the copilot fee input and its layout column for task challenges. - Keep copilot assignment and the rest of task billing unchanged. - Preserve the copilot fee input for non-task challenges and document the task-only restriction. Any added/updated tests - Added form coverage that verifies task challenges hide the fee while retaining copilot assignment and billing. - Added coverage that verifies non-task challenges still show the fee.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What was broken
Task challenge setup in the Work app displayed a Copilot Fee field, allowing project managers to bundle a copilot payment with the task instead of recording the copilot work as a separate task payment.
Root cause
The challenge editor rendered the copilot fee input for every billable challenge without considering the resolved task challenge state.
What was changed
Any added/updated tests
origin/devbaseline: 18 suites and 32 tests fail both before and after this change. This branch adds two passing tests, increasing the passing total from 999 to 1001 without adding failures.