Upgrade task fails when using requirement numbers above 2bn

Fix versions

Priority

Description

A customer has REQ-3690081058, and, since it is above 2bn, the key can't be parsed as an 'Integer'. Therefore the upgrade task fails.

  • We'll increase the size of requirement keys to long (max will be ~ REQ-90000000000000000, if they need more, they need to split the number with an underscore/dot/any character).

  • That will also allow the suggestions to work with such high numbers.

Activity

Show:
Resolved

Details

Assignee

Reporter

Release date

Affects versions

Requirement Yogi

Created March 11, 2022 at 10:43 AM
Updated April 19, 2022 at 6:03 PM
Resolved March 11, 2022 at 10:44 AM