You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[COMMS-843] Make Target Versions the default for new installations (#24690)
* [COMMS-843] Remove the work_package_multiple_versions feature flag
* [COMMS-843] Enable multiple target versions per WP by default
* [COMMS-843] Pin specs that relied on multiple versions being off
With the setting now defaulting to on, specs describing the legacy
single-version behaviour no longer get it implicitly. State the
assumption where it is load-bearing: contexts named "inactive"/"off"/
"disabled", the single-value validation rule, and the surfaces that
expose the deprecated version column (query columns, query form API,
PDF export, grouping and sorting by version).
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* iron out the test coverage a bit
* appease rubocop
* [COMMS-843] Read the target version links via parse_json
`response.parsed_body` is not available here: these are rack-test
requests, so `response` is a Rack::MockResponse. Use json_spec's
`parse_json`, which reads the body without tripping
Rails/ResponseParsedBody.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* [COMMS-843] Pin the feature specs covering the single version field
Same reason as the unit specs: with the setting on by default, the work
package form, table columns, sort options and form configuration expose
target versions instead of the deprecated version, so the specs
describing the single-version UI have to say so.
Whole spec pinned where the version attribute runs through all of it
(baseline rendering, form configuration, assign_versions permission),
single example or context where it does not.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* [COMMS-843] Exercise the target versions field on the new default
Two of the pinned specs already drove the targetVersions field; they only
needed the version to exist before the page loads, since the multi-value
field resolves its options then, unlike the single-value one. Create it
eagerly and drop the pins, so both cover the default again.
Also cover the form configuration with the feature on, which had no
feature-level coverage left: target versions is offered in place of the
deprecated version and can be dragged out of the group.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* [COMMS-843] Restore the pins on the work package form specs
Creating the version before the page loads was not the reason these
specs failed: the target versions autocompleter in the work package
full view offers no options at all while multiple versions is enabled,
so nothing can be picked by name. Pin them back to the single version
field, which is what they describe, and leave the empty autocompleter
to be looked at on its own.
The form configuration coverage added alongside stays - it passes.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* remove some old flag references
* pin some more tests after merge from dev
* pin last test
---------
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
0 commit comments