Reported Bugs

Make the current state, future state fields optional

Idea sent by Sara Hinton - RGA project. This is because the project is just capturing the change delta based on the Regulatory mandates.

  • Sapna Singh
  • Mar 21 2019
  • Shipped
  • Attach files
  • Guest commented
    April 22, 2019 19:05

    This would also be helpful if one of the fields is not yet determined/defined.

    Some of our change impacts are TBD in some way -- either we don't know what the future state will look like yet, or we don't know which go-live it will occur in. We made "TBD" phase options for this and assigned those phases random dates, which skews our data. Can we add a "TBD" placeholder that doesn't require dates? Or seemingly we should just be holding these somewhere offline.