-
Project item journals are unable to post in next open ledger period with “Automatically set accounting date to open ledger period” parameter on
Suggested by Alfie Ta (Tek Experts) – Needs Votes – 0 Comments
With the “Automatically set accounting date to open ledger period” parameter on in Project management and accounting module, it should allow user to post journals (Hour, Item, Expense, and Fee) in unopened period. However, it works for Hour, Expense and Fee journals, and blocked only Item journals.
-> This issue causes lot of additional work to the users to change the transaction dates for every work order line and process the work order once again through Field service integration
-
Dynamics 365 Project service order per planned priority tasks scheduled resources expenses preferences
Suggested by Francisco Orozco – Needs Votes – 0 Comments
Wish there is an option to easily schedule and priority tasks expense resources process transaction planned tasks as per priority or priority role origin preferences, for purpose to maintain user role, planned and expenses priority tasks, for purpose to potentially justify main project goal (s) or feedbacks.
-
Change Schedule mode on task
Suggested by Hans-Peter Dinser – Needs Votes – 1 Comments
It should be possible to change the pre selected Schedule Mode from the Project Header on the task. This makes it easier to plan task deppending on the different requirment of work.
Example. If the shedule mode on the project header is "Duration" and I have a task where I want the system to change the duration based on the effort, I want to change this single task to schedule mode Effort.
I think this functionality was available in Project Service Automation
-
Default Auto Scheduling Off
Suggested by Laura Mikulski – Needs Votes – 0 Comments
Allowing a setting where Auto Scheduling in WBS is defaulted to off.
-
Configurable default unit for Task duration in Project form Task tab
Suggested by Takamitsu Endo – Needs Votes – 0 Comments
Current behavior:
Default unit for Task duration is not configurable. If we put just "1" in duration column, it will automatically be "1 day"
Ideal behavior:
Default unit for Task duration is configurable (with user setting or global setting). We can change a default duration so we don't need to type "h" or "hour" in duration column every time.
Background/problem:
Depending on the usage and business, the most frequently used units of task length vary. Some people use "day" most, others may use "hour" or "week". For those who almost always use "hour", entering "hour" (or even "h") in task duration every time can be a hassle.
In addition to that, in Japanese environment, "hour" or "h" doesn't work. User should enter "時間" (means "hour" in Japanese) every time. Actually this requires many key types.
To do this in Japanese environment, basically user needs to type at least
- ` (to change input mode from English to Japanese)
- j
- i
- k
- a
- n
- [Space] (to transform "jikan" to "時間")
- [Enter] (to fix the input)
Doing this every time is quite a burden especially there're many tasks.
Please consider to make a default unit for Task duration configurable.
-
Allow linking of WBS to GitHub Issues
Suggested by Henry Staples – Needs Votes – 2 Comments
As a software development firm, our engineering teams track all their work items in GitHub Issues (and GitHub Project == Agile Project Iteration). We have an overarching WBS for the company. Within our engineering, we'd like to have a project iteration schedule in Dynamics ProjOps with sub-items that link to the applicable GitHub Issues. ***Then*** we would like to have eng team enter their hours for the GitHub Issue item and that roll-up into the WBS work package.
So, our WBS would look like this ==>
Company
Engineering
Project 1 Iteration 1
Work Package 1
GitHub Issue 1 (eng team tracks hours here)
GitHub Issue 2
GitHub Issue 3
GitHub Issue 4
Work Package 2
GitHub Issue 5
GitHub Issue 6
If you can accomplish this, then we could do away with some homegrown tracking methods and replace fully with GitHub and Dynamics ProjOps. Please contact me if you have any questions.
-
Make the Schedule Board Project-Aware
Suggested by Wayne Walton – Needs Votes – 0 Comments
The Schedule Board, in its current layout, has no way to pivot on projects. For example, if I am a scheduler, and I need to make sure a project is completely staffed and scheduled before I release it to start, while also looking at other concurrent projects to see how staffed they are, there is simply no way to do that on a project level in Project Operations.
With the primary pivot being around resources and tasks, there's no easy way to validate that a project is fully staffed from the schedule board.
-
Planned resources display in resource fulfillment grid
Suggested by Oussama Kamal – Needs Votes – 0 Comments
In the Resource fulfillment form, the display is based on availabilities for Planned resource and Available resources sections. It would very helpful if resource planners can choose to have a view based on Reserved hours and Remaining hours to fulfill or each section (Planned resource and Available resources).
-
Confirmation for resources deletion from project team
Suggested by Oussama Kamal – Needs Votes – 0 Comments
When user want to delete a resource from the project team and scheduling, he may select multiple lines by mistake and all the selected lines are deleted. A pop-up message for deletion confirmation may be very useful to avoid replaning resources.
-
Allow a default setting for the timescale in project planning - either hours, days, weeks, months
Suggested by Harald Jabinger – Needs Votes – 0 Comments
Our employees work on projects that span many months up to several years. When planning, analyzing or updating a project they typically consider months as a timescale. However, PSA (PO accordingly) provides any time-phased data in the week view, this needs to be switched to months view each time.
Project Service Automation currently does not support the ability to default the time scale in views for project planning and resource planning. Users must always set the timescale to meet their needs - in case of hour, day, month (i.e. different to week).
The only exception is the time schedule grid (maintain bookings), that can be defaulted to months for the entire organization. While it keeps the possibility to switch to another scale by user and session in case it is required.
With the upgrade to Project Operations, scheduled to start in late 2023, we would like to have the ability to default the time phased views globally for consistency of the user experience und to reduce the number of clicks to change it.
The areas where the time phased data are accessed from the project main form:
- Grid Table - Contour assignment editing
- Project Timeline/Gantt
- Project Cost & Sales Estimates
- Resource Reconciliation
- Resource Requirement Details in specify pattern
- Maintain existing bookings