Aller au contenu principal

Creating Service Assets

A Service Asset makes a Project Planning Line available in Jira as a Jira Assets object, so it can be attached to a Jira work item - for example as a custom field of that object type - and used there for automation or manual selection. A typical case is a recurring Subscription such as Maintenance or Support linked to a Project: creating a Project Planning Line for it with a Service Asset makes that planning line selectable on Jira work items. DYCE Time Tracking recognizes such a selection through the Service Asset's Job Planning Line ID attribute (the Business Central system ID of the underlying Project Planning Line) and, when present, presets a new time recording with the corresponding Project, Project Task and Project Planning Line.

A Service Asset can be created automatically while creating a Project Planning Line, or manually afterwards; both ways create the same kind of record, synchronized to Jira the same way once table and field mapping for assets is set up.

Creating a Service Asset while creating a Project Planning Line​

In the Create Project Planning Line wizard, a Service Asset section offers a Create Service Asset toggle and a Title field, pre-filled from the planning line's description once a project and item are selected. Enabling the toggle and confirming the wizard with OK creates the Project Task, the Project Planning Line, and the Service Asset in one step.

Creating a Service Asset manually​

Use Create Service Asset on a Project Planning Line to open the Create Service Asset page:

  • A read-only section shows the Project Planning Line's context: Customer, Project No. and Description, Project Task No. and Description, Item No., Planning Line Description, and its source (see Source granularity below).
  • If the planning line's source is a Contract or Subscription and no specific line has been chosen yet, a Contract Line / Subscription Line field allows picking one - it is left blank to create the Service Asset at the Contract/Subscription header level instead.
  • In the Service Asset section, a Title (required, pre-filled from the planning line or the chosen contract/subscription line) and an optional Long Description are entered.

Confirming with OK creates or updates the Service Asset. Create Service Asset stays available on the Project Planning Line as long as a Service Asset can still be created at a deeper granularity than what already exists for that line; once every available level already has a Service Asset, the action is no longer shown, and the existing Service Asset is opened and updated through the same page instead.

Source granularity​

A Service Asset always records where it comes from, as one of:

  • Project Planning Line - the default, used when the line is not linked to a contract or subscription.
  • Contract, Subscription or Subscription Line - used when the Project Planning Line was created from a Customer Subscription Contract or a Subscription, at the deepest level available: the specific line, if one was chosen, otherwise the contract or subscription header.

The context copied onto the Service Asset - Customer, Project, description, quantity and so on - is kept up to date automatically as the underlying Project Planning Line, Project Task or Project changes.