OnePlan Release Notes - June 9, 2023

• You can now create work plan notifications. Notifications can be sent immediately, or in a daily or weekly summary. The notifications are configurable. For example, you could send a notification to the assigned resource if a task is not yet complete, and the due date has passed. You could send a notification when a resource is assigned to a task. Notifications can be global (for all plans), or just for you/your plan.
  
• You can now bulk edit work items. For example, you could select multiple tasks and update their status to “Completed”.
  
• You can now assign resources to tasks much easier. Simply drag and drop resources from the new resource grid or from the resource usage window.
  
• You can now create and update muti-choice work plan fields.
  
• When using the filter choice field option (cascading choice fields), the filters now work in the work plan list view. Previously, this only worked in the quick edit form.
• When using the add subtask option in the work item contextual menu, all work item types are now available.
• You can now add and update the inactive field from the work plan list view.
• If you have executive-level permissions, you can now only save personal views. Previously you could save global views.
• If you split a task, and then delete the split tasks, the task will automatically be changed back to a normal task. Previously you would need to delete and recreate the task.
• When copying and pasting tasks, timesheet hours will no longer be copied to the new tasks.
• You can now create baseline duration fields (for example Baseline1 Duration).

Related Articles

• Create Work Plan Notifications
• Bulk Update Work Items in the Work Plan Grid
• Assign Resources to Work Items in the Work Plan Grid
• Manage Plans in the Work Plan Grid
• Create and Edit Fields

• You can now speak to Sofia, just click the new Microphone icon and ask away.  
• Sofia can now provide insights on @OnePlanData in My Work.
• Sofia can now provide insights on @OnePlanData in the Work Plan Kanban Board.
• Sofia can now provide insights on @OnePlanData in the Portfolio Kanban Board and Portfolio Roadmap.
• Sofia can now provide insights on @OnePlanData in the Portfolio Modeler analyze window.
• Sofia can now answer questions about the oneplan.ai company website.
• A copy button has been added to easily copy and paste text responses created by Sofia.
  

Data Audit Logs

• You can now view Audit Logs that are more than a month old. Previously, you could only view up to a month in the past.

• The initial load of OnePlan is now faster than ever before. This is especially true when loading groups that have thousands of resources.
• If you try to filter on a choice field with thousands of choices, the field will now load the choices much faster.

OData

• You can now report on work item dependencies. There is a new table named "TaskDependency" which can be joined to tasks to visualize dependencies.

• You can now update the status of a time off request via the time off PATCH API call.

Smartsheet Integration

• Added support for the predecessor field with lag time. The Task Dependency OnePlan field can be mapped to the Predecessors field in Smartsheet.

Related Articles

• Smartsheet Integration - Integration Setup
• Smartsheet Integration - Default Field Mappings and Scheduled Strategies

Tabular Data to OnePlan Resource Planner Integration

• It is possible to specify if existing resource plan data should be removed when the integration runs.
• A new "Do not remove existing data" configuration setting was added. The default value is to remove all data before the new data is imported.
• A new configuration setting was added to specify the scope of the data removal. The options are "Included Resources" or "All Resources" The "All Resources" is the default setting.
  The Included Resources options removes OnePlan resource plan data only from resources that are included in the csv file.

OnePlan Plans and Azure DevOps Epics Integration

• Added support to automatically remove a backlog item mapping from OneConnect if an item has been deleted from ADO.
• Added support for identity fields. If an ADO identify field is mapped to a OnePlan user type field, then the resource will be set in OnePlan during the sync.
• Added support to sync choice field values from OnePlan into ADO. All that needs to happen is that the choice fields be mapped within the PickListLookup table and the SyncLookupToADO strategy will populate the OnePlan values within the ADO choice field.
• In the "Connect to ADO" dialog in OnePlan, the ADO item drop down is now sorted alphabetically.

Related Articles

• Azure DevOps Epics Integration - Integration Setup
• Azure DevOps Epics Integration - Default Field Mappings and Scheduled Jobs
• Azure DevOps Epics Integration - Recommendations and Best Practices

OnePlan Plans and Azure DevOps Plans Hierarchy Integration

• Added support to automatically remove a backlog item mapping from OneConnect if an item has been deleted from ADO.
• Added support for identity fields. If an ADO identify field is mapped to a OnePlan user type field, then the resource will be set in OnePlan during the sync.
• Added support to connect an existing Plan item to both the top and child plan level plans. As an example, you can connect a Feature Plan to a Feature item that is child of an Epic in ADO, that Feature will now show up in the dropdown menu on the connected systems screen. Previously, in this scenario only Epics were listed.
• A new strategy called "OnePlanPlanItemsCleanUp" was added to support the automatic removal of deleted backlog items. This new strategy queries OneConnect item mappings to confirm if the task/backlog item in Azure DevOps exists. If the task/backlog item in ADO does not exist, then the task/backlog level items will be removed in OnePlan.
• Additional logging was added if a resource cannot be created in OnePlan from an ADO item.
• In the "Connect to ADO" dialog in OnePlan, the ADO item drop down is sorted alphabetically.
• OnePlan backlog items that are mapped to ADO items are editable now.

Related Articles

• Azure DevOps Plan Hierarchy Integration - Integration Setup
• Azure DevOps Plan Hierarchy Integration - Default Field Mappings and Scheduled Jobs
• Azure DevOps Plan Hierarchy Integration - Recommendations and Best Practices

OnePlan Plans and Azure DevOps TeamProjects Integration

• It is possible to specify the value for the Version Control field in ADO for newly created items. There is a new Version Control dropdown setting in the configuration. Creating new plans in ADO from OnePlan will set the Version Control for that Team Project in ADO.
  Options are: TFVC or GIT. (TFVC being the default)
• Added support for identity fields. If an ADO identify field is mapped to a OnePlan user type field, then the resource will be set in OnePlan during the sync.
• Added support to sync choice fields from OnePlan into ADO.
• OnePlan backlog items that are mapped to ADO items are editable now.  

Related Articles

• Azure DevOps Team Projects Integration - Integration Setup
• Azure DevOps Team Projects Integration - Default Field Mappings and Scheduled Jobs
• Azure DevOps Team Projects Integration - Recommendations and Best Practices

Jira Project and OnePlan Plans

• Support to connect to an existing Jira Project was added to OnePlan.
• OnePlan backlog items that are mapped to Jira items are editable now.
• Added support to automatically remove an item mapping that has been deleted from OnePlan or Jira.
• There was a checkbox to indicate if we should use Classic or Next-gen Jira APIs. It is automatic now.

Jira Epics and OnePlan Plans

• OnePlan backlog items that are mapped to Jira items are editable now.
• Added support to automatically remove an item mapping that has been deleted from OnePlan or Jira.
• There was a checkbox to indicate if we should use Classic or Next-gen Jira APIs. It is automatic now.

OneConnect Administration Portal

• The "Alternate OnePlan Environment URL" configuration property that is displayed as free form text for a OnePlan integration was updated to be a list options.
• The field mapping page sorts both the field list in the dropdown and the configured fields on the page alphabetically.
• The delta job type (full or incremental) was added to the job schedule list screen.
• The filter icon is blue and bold if a filter is set on a strategy on the job schedule list screen.
• A new "None" scheduled type was added for integration jobs. When a schedule type is set to "None", it will not be executed automatically. This is useful for jobs that are usually executed manually.
• It is possible now to close the execute strategy dialog once the job started.
• Legend was added to the job status field to clarify the different type of job statuses.
• A new job status was added called "Success with exceptions". If an integration job has processing errors, but it processes at least one item, then the status will be set to "Success with exceptions". If the integration job processes no items, then the job status will be set to "Failure". If all items are successfully processed, then the job status will be set to "Success".