Skip to content

Add bigint fields for epic descendant weights

Michael Trainor requested to merge tmike-graphql-bigint-epicdescweights into master

What does this MR do and why?

Sum of issue weight can exceed the Int datatype maximum, causing an integer out of bounds error.

Deprecating the Int fields and introducing new fields with BigInt type.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

  1. Create a group and project in that group
  2. In the project, create an issue with a weight of 2147483647
  3. In the project, create another issue with a weight of 1
  4. In the group, create an epic and add the two created issues.
  5. Navigate to Plan > Epic boards

This MR doesn't change the behaviour or handling of integer values above 2147483647. The steps above will still result in an out of bounds error. This MR deprecates the int fields, and introduces new bigint fields. Consumers of the deprecated int fields will be migrated to the bigint fields in subsequent MRs to avoid the out of bounds error.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Michael Trainor

Merge request reports