Attached the details of simple suggestions to improve the resource assignment screens in project module. For a long time I thought they did not work. Turns out it is a matter of the wrong fast tab being open when you come in.
The other improvement is the "retention' of user settings for the period in the setup screen. The system should remember that user A always looks at things in monthly view, user B in weekly view. The system is now reverting to always weeks in one screen and always days in another . See attached.
Comments
Project module D365.
Resource availability screen.
- When approached from the main menu, the screen shows like this
The Fast tab “reservation details” should not be open by default. Because no resource is highlighted, it shows nothing. The screen should show up with the resource availability tab open, like this
NOTE: the system does not remember user settings for this screen, so every time I come back, I have to close that reservation details tab first before getting to work.
- The “view settings” are partially remembered by user. The sliders yes/no are remembered but not the time period. It will go back to ‘weeks’.
- If I open the Resource assignment form from a published WBS task, I get this
A little better than the previous case but here we find ourself in an awkwardly narrow look for our resources assignments tab, only one resource shows, we have to close Task Details first. It would be more logical if Task Details is closed coming in. the task description is spelled out in big font in the top of my screen. No risk there. So the screen would look like this
Now we can get to work selecting people.
The setup in this screen has the strange behavior of always reverting to “day”. It does not remember a user setting for that field, only for the two sliders.
This set up should remember the user’s last used value.
HOW TO ATTACH SCREEN SHOTS?
Category: Project Resource Management
Administrator on 5/6/2019 4:00:56 PM
Thank you for your feedback. This is a great suggestion! We will consider this in our roadmap.
Sincerely,
Kim Nelson
PM, Microsoft