Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

When approvals are entered by users they remain in the saved status until they are submitted. Saved approvals are only visible to source supply teams. Approvals remain in a saved state so that they can be reviewed at a holistic level by source supply teams.

Once ready, you can transition approvals from saved to submitted. This is a batch process that will submit all saved approvals for the parent source supply team and all child teams of the parent. Once submitted the approvals are visible to the target demand teams.

Instructions

  1. Locate the

...

  1. supply team or the parent

...

  1. supply team using the Team's search.

  2. Select Planner.

  3. Planner lists the requests and saved approvals for the

...

  1. demand teams. The value on the left is the current full-time equivalent (FTE) amount the

...

  1. supply team is providing to the

...

  1. demand team. The centre value is what has been requested by the

...

  1. demand team following by the difference between the current and the approved to highlight any requested change.

  2. Review the approvals, making any changes as needed.

  3. To submit the saved approvals to the

...

  1. demand teams, in the action bar click Submit all approvals.

    Image Modified
Tip

The approvals are now submitted. The target demand teams can see the approvals from the source supply teams.

Filter by label (Content by label)
page
showLabelsfalse
max5
spacescom.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@9e4
showSpacefalse
sortmodified
showSpacetypefalsepage
reversetruetype
labelsplanner request submitting resources target-team source-team
cqllabel in ( "source-team" , "submitting" , "resources" , "planner" , "request" , "target-team" ) and type = "page" and space = "OS"labelsplanner request submitting resources target-team source-team
Page Properties
hiddentrue

Related issues