What is the challenge? |
If a release has a multiple waves with the same name (e.g., "Custom") OR waves with the same date (e.g., Beta - 2 & GA - 1 both release on March 10), then the duplicative cells (name or date) are combined and do not line up against the correct wave/date If we move the waves to be rows rather than cells, then the rows are repeated multiple times creating duplicative release line items and extremely long and unusable reports. |
What is the impact? |
There is heavy manual effort to realign Waves and Dates to make sense of and confirm releases. We cannot surface the release report to clients as a webpage, as the information is often misleading or inaccurate. This means we have to continue with a manually created weekly document to update users on upcoming releases or will have to build a new report in a different application like PowerBI to surface to clients. |
Describe your idea |
Don't de-dupe cells for Release Waves & Wave Dates, similar to how an XLS doc would show them |
Sorry, I thought that "Wave" may have been custom terminology for release phases. I see now from your ticket last year that these are custom table cells. I believe the duplicates are being caused by the "Wave type" field. I am going to merge this idea with a related idea for reducing duplicate values in pivot tables. https://big.ideas.aha.io/ideas/A-I-8390
This creates insane duplicates in all cells and is not a fix.