Spaces

Teams work in 'spaces' to represent the team the work is owned by. From time to time to time we have cross functional projects - and it would be good to set up one project that all assets could be added to. The problem is that because people work in spaces - we'd still want the affiliation to the space to remain. For example Team A, Team B and Team C are all working on tax year end changes. Team A have all their assets in Team A space and likewise. However ideally we want to create ONE tax year end project for all assets impacted from all three teams. BUT when team A works within their space for example pulls a report of all assets, this asset will still show. I know we can do reporting from All assets and use asset owner - but users tend to use their space.

Although there is some ability - it's limiting - and having more ability would help for the instances when you may need to see more on a screen. In screenshot - the pink highlight - shows I can on some columns I can make thinner than the column title. But in some others the column title limits the width. The name is a funny one - I can make it thinner - but the title reduces and the white space remains! There are situations where I want to see more information on screen.

Users would appreciate the ability to move a project to a different Space. In doing so, they expect assets within that project to travel to the same (new) space, because: This will put those asset on the radar (visibly) of the new space They can decommission/remove the old space They can respond to reorganisational changes (when spaces are organised by department/division) adequately Changing the Space 'parent' of an asset currently poses a technical challenge in the back-end