A saved request is when a demand team user has entered a full time equivalent amount but the request has not been made visible to the supply team. Requests remain in a saved state so that they can be reviewed at a holistic level by demand teams. Once ready, requests transition to submitted requests by a user submitting them. This will process a batch of saved requests which will then be visible to supply teams.
A saved approval is when a supply team user has entered a full time equivalent amount but the approval has not been made visible to the demand team. Approvals remain in a saved state so that they can be reviewed at a holistic level by supply teams. Once ready, approvals transition to submitted approvals by a user submitting them, This will process a batch of saved approvals which will then be visible to demand teams.
Related articles
| Filter by label (Content by label) |
|---|
| showLabels | false |
|---|
| max | 5 |
|---|
| spaces | com.atlassian.confluence.content.render.xhtml.model.resource.identifiers.SpaceResourceIdentifier@9e4 |
|---|
| showSpace | false |
|---|
| sort | modified |
|---|
| type | page |
|---|
| reverse | true |
|---|
| labels | planner saved request approve submitting |
|---|
| cql | label in ( "submitting" , "planner" , "request" , "approve" , "saved" ) and type = "page" and space = "OS" |
|---|
|