I’m having issues with request classes on work tasks. We created a project (including work location). But now, when we create a task from the project, very few of the values (including work location) are mapped onto the null work task. The drop-down that comes from the request class depends solely on this work location.
Also, the work location of the task gets its value from the project (as mapped). But now, when we try to get the drop-down for the request class based on work location, random values are shown. When I reselect the same work location, and then go back to the request class, I see the correct values. Any thoughts on this behavior? How do you get the request class list for the very first time without reselecting the work location in a work task that was created from the project?
[Admin: To see other related posts, use the Mapping tag or Work Tasks tag.]
When the Operations team was changing a job plan, the wrong date was entered, and it created over 1,800 work tasks. They have since tried to retire them and they changed to Draft status. To get rid of these, can the job plan itself be retired?
[Admin: To see other related posts, use the Job Plan tag.]
I’m looking for some information on how others have addressed the tracking of activities like meetings, training, and other off-stage activities without recording this time against a standing open work task?
[Admin: To see other related posts, use the Work Tasks tag.]
If a work task has a calendar and the “Planned End” or “Actual End” date-time field values are updated, the “Working Hours” are not always calculated correctly. The working hours do not seem to factor in the calendar hours.
The working hours were not being calculated correctly. The issue was that the values for the calendar fields (Year, Month, Day, etc.) were not being set correctly. The fix was to set the calendar fields exactly as we do for the other calculation methods. Moving forward, we resolved a work task record and Gantt chart issue, where the Actual Working Hours and Actual Working Days were not being correctly calculated when an Actual End date value was entered.
[Admin: To see other related posts, use the Calendar tag or Gantt tag.]
I was wondering if there is a way to set the PM work schedule for every 2 years, maybe even 3 or 4 years?
When entering the schedule for a PM task, you would think that you could select the Recurrence Pattern Type of “Yearly”, and then enter every 2 years, 3 years, and so on, but no, you can’t! One rather cumbersome solution is to enter a yearly schedule (i.e. every year) and then set a number of exception dates for the years when you do not want the task to happen. That is a bit awkward.
The better, but less obvious, solution is to choose the Recurrence Pattern Type of “Monthly”. This offers two options to set the schedule to either “Day [x] of every [x] months” or “The [first] [Monday] of every [x] months”. Choose whichever one suits your needs, and set the “every [x] months” value to every 24 months, 36 months, 48 months, etc. The main downside of this is that the word “Monthly” appears in the name of the tasks produced, which is misleading when the schedule is effectively based on a number of years.
[Admin: To see other related posts, use the Preventive tag or Scheduling tag.]
In TRIRIGA, why doesn’t my dependent task go any further than the planned end date, if I move the parent task beyond the planned end date?
The task that is being moved (along with its dependent task) eventually violates the planned end constraint. The task that is in violation of the constraint is in red, and the dependent task will not be moved past the planned end. If there is no planned end, then there is no constraint and you can freely move both tasks.
[Admin: To see other related posts, use the Gantt tag or Scheduling tag.]