Can you retire a job plan to get rid of unneeded draft work tasks?


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.]

Continue reading

Advertisements

How do you set the PM schedule for every 2, 3, or 4 years?


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.]

Continue reading

Why doesn’t dependent task go further than planned end date?


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.]

Continue reading

IV97411: Adjusting task status on Gantt not working uniformly


Adjusting the task status on a Gantt chart with Ctrl/Cmd+click is not working uniformly across client operating systems.

We needed to disable the Ctrl+left/right-click and Shift+left/right-click, which are not working consistently across browsers and Mac, and reintroduce the right-click > “Set Percentage Complete” to the right-click menu. We also needed to update the “Percent Complete” message to be shorter, and update the message minimum width to be wider.

Moving forward, we removed the ability to set the percentage complete by using Ctrl+click, which does not work correctly on all browsers on all operating systems, replacing it with the ability to “Set Percentage Complete” by using the right-click context menu when right-clicking a Gantt task.

[Admin: To see other related posts, use the Gantt tag.]

Continue reading

IV97245: Gantt section not keeping the associated report sort order


In a Gantt section, the section is not honoring the associated report sort order.

The issue was caused by the dynamic ordering that was implemented by the project tasks’ internal tree set. The BO query comparison was performed by using the string form of the columns. Moving forward, we resolved an issue where the default Gantt sort ordering, and the sort ordering immediately after importing an MPP project file, did not correctly order by the sequence ID based on the Gantt section query configuration.

[Admin: This post is related to the 06.14.17 post about task date issues when importing MS Project (MPP) files. To see other related posts, use the Gantt tag.]

Continue reading

IV97243: “Apply Record” and “Apply Template” use current time stamps


The “Apply Record” and “Apply Template” methods use current time stamps, instead of source-record time stamps when mapping to the created tasks.

We needed to make modifications to use a Query task to grab all associated tasks and task templates on the target record, and call two workflows against each to force updates to the Planned Start and Planned End dates within the context of their associated calendars. Moving forward, the application now correctly applies the task calendar hour restrictions to the tasks and task templates when using the “Apply Template” and “Apply Record” functionality with capital projects.

[Admin: To see other related posts, use the Templates tag or Calendar tag.]

Continue reading