Issue when reverting to a prior version of a plan, or when importing a plan, only when value expansions expand the parameter values with the same name in different parameters

A true classic of a pair-wise defect. Put this one in the dictionary as a canonical example of the term.

Editing project name of current plan's project

Editing the name of the project that owns that plan you're in from the Edit Project dialog would make the share link on the plan's page stale.

Parameter name change warning in bulk edit

The warning about parameters used in auto-scripts being changed in a bulk edit is now more specific and more helpful.

Hexawise Capture on internal URLs w/o a TLD

Thanks to Caleb for reporting the limitation.

More consistency in requirements expected outcomes and auto-scripts expected results throughout the Excel export

Thanks to Mary-Anne for reporting the issue.

Value expansion preservation across multiple parameters that have the same value, after a bulk edit

Thanks to Keith for reporting the issue.

Editing value expansions from the mind map view

Sticky highlighting of test cases when clicking on them in the test cases view

Bad revision dialog state after revert is complete

Select between staying with the original plan or using the new copy when copying a plan

Changes to Hexawise Automate test script didn't update test plan modified date

Auto-completion of Gherkin script syntax in Hexawise Automate

Search for projects by name

The search field in the "Your Plans" dialog now searches for matching plan names and project names.

Auto-scripts expected results regression

Using "Relax" feature in auto-scripts before saving the first step

Previously this did not work, but now it saves the first step then proceeds with the "Relax" auto-script generation feature.

Duplicate value pair can be created in some scenarios

Test case sorting and required paramater values

Fixed a pairwise defect where test cases sorting by a parameter where some of the test cases had a value forced by a requirement was impacted by the UI styling that was done on the forced parameter value effecting the sort order.

Override browser's language with a user profile setting

Incorrect share info after initial project creation

Immediately after creating a new project, the UI would report the project was shared with 1 person, even if it wasn't.

Numerous requirements ordering issues

All new requirements UI

The UI for forcing specific interactions to appear in test plans has been completely revamped to be easier to use. The main goal of this rework was to eliminate all of the horizontal scrolling that had to happen on larger plans with more parameters. The new UI is a single page wide, no matter how many parameters you have. While working on this main goal, we made numerous other improvements:

• drag and drop re-ordering of parameters
• Google sheets / Excel-like data grid for ease of editing, full keyboard only support
• refined terminology that is more clear, "forced interactions" and "expected outcome"
• auto-saving (type ESC to cancel your changes)

Some UI glitch regressions in the test case count and pairwise explanation tooltips and dialog

Achievement counts are now displayed for 4th and 8th plan achievements

Export file naming

Now uses underscores for special characters that are dropped from the filename rather than simply removing them.

Auto-scripts test preview selection

You can now sort the parameters in the test case preview selection table for auto-scripts. The header is fixed as well as you scroll the test rows.