Requirement keys should not have trailing spaces

It should not be possible to create keys with trailing spaces like ABC-002 . It seems to make the indexation fail.

Implementation

• In the software, make it impossible to create requirements with space keys ending with a space:

  • The new indexation is quite literal with trailing spaces, and shouldn’t be,

  • The insertion shouldn’t let the user add trailing spaces either.

• Write an upgrade task, that will go through every record, and check if there are trailing spaces,

  • It will remove the trailing spaces,

  • If there is a separate record for the same requirement with and without trailing spaces, it will merge them. That means if 'MCRE-001' and 'MCRE-001 ' both have a property named “Prop1”, then one of the values will be deleted when it gets merged into 'MCRE-001'. If both requirements have the same links and dependencies, they will both be attached to 'MCRE-001',

  • If requirements in baselines have trailing spaces, we’ll also remove the spaces and merge them if there is also a version without trailing spaces. It will change data in baselines.

Things to changes:

• Frontend to not allow whitespace

• Backend to trim the requirement key

• Upgrade task