"Issues in Epic" view need to be updated with team column due to introduction of Jira align

"Issues in Epic" view need to be updated with team column due to introduction of Jira align.

Imagine in an organization so far there were 10 teams (each team has one Jira project - where they can create all issue types under Feature/Epic). These all projects are connected to the Program/ART project - where one can only create Features. With this Way of working- so far it was very easy in "Issues in Epic" view to recognize which issues belongs to which team and each issue had the key prefix belongs to certain team project. But Now..... Jira Align came into picture with the constraint that 1ART can have only 1 Project where we will create features and all issue types below it. Due to this now all issues under feature has same prefix. Due to this now its very difficult to use "Issue in Epic" view because we dont know which issue belongs to which team. With the addition of Team column in this view, this problem can be solved easily. As an organization when Atlassian propose solution to the companies then Atlassian should also consider these kind of use cases before launching any new tool. Lets make it user friendly in the sense that tool works for user and not other way around.