Versions Compared

Old Version 25

changes.mady.by.user Space Sync for Confluence

Saved on

compared with

New Version Current

changes.mady.by.user Space Sync for Confluence

Saved on

Key

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

...

Default principle sets can be defined per team type via Settings / Org Structure type config. Select a team type, then choose a preferred principle set for that team type.

...

JSON parameters for Principles:

Member Count

parameter maxMembers(optional), minMembers(optional)

title Should consist of no more than ${maxMembers} direct members.

...

Note

Note that the default principle set is applied to teams that are updated after the default is set. All existing teams will not be automatically updated when the default is changed.

One way to ensure all teams are updated is to import teams with the principle set ID updated. For example, the Teams CSV import can be used to assign a principle set ID to each team in the system.

...

JSON parameters for Principles:

Member Count

parameter maxMembers(optional), minMembers(optional)

title Should consist of no more than ${maxMembers} direct members.

Should consist of between at least ${minMembers} and direct members.

Should consist of between ${minMembers} and ${maxMembers} direct members.

...

Code Block
      {
        "type": "FIELD_MATCH",
        "args": {
          "field": "country",
          "min": 8,
          "max": 10,": 10,
          "metric": "count"
        }
      }

In the above, if there are any values for the country field where less than 8 or more than 10 people have a matching value the principle evaluation fails.

Also supports signal overrides.

See Role Tag Parameters for details on the roleTagType and roleTagAttribute parameters.

Demand Allocation Ratio

parameter minAllocationRatio,maxAllocationRatio,includedTags,excludedTags,fteThreshold,includeVacancies,useFteRatio

title <%- actualAllocationRatio %>%</strong> members are allocated to demand structure.

Code Block
{
            "metric"type: "countDEMAND_ALLOCATION_RATIO",
        }    args:   }

In the above, if there are any values for the country field where less than 8 or more than 10 people have a matching value the principle evaluation fails.

Also supports signal overrides.

See Role Tag Parameters for details on the roleTagType and roleTagAttribute parameters.

Demand Allocation Ratio

parameter minAllocationRatio,maxAllocationRatio,includedTags,excludedTags,fteThreshold,includeVacancies

title <%- actualAllocationRatio %>%</strong> members are allocated to demand structure.

Code Block
{{
              fteThreshold: 0,
              includeVacancies: false,
              typeincludedTags: "DEMAND_ALLOCATION_RATIO"[],
            args  excludedTags: {
              fteThreshold  NON_PACE_ALLOCATION: 0[],
              includeVacancies  RESOURCEAVAILABILITY: false[],
              includedTags  NON_PACE_ALLOCATION_DEFAULT: [],
              excludedTags:},
{                 NON_PACE_ALLOCATIONincludedTeamTypes: [],
                RESOURCEAVAILABILITYexcludedTeamTypes: [],
                 NON_PACE_ALLOCATION_DEFAULT: []"Working With Agile"
              }],
              maxAllocationRatio: 100,
              minAllocationRatio: 90
            }
          }

Notes:

  • useFteRatio - default is false. When set to true the ratio is calculated from the sum of allocated FTE (with over allocation ignored) as a percentage of total available FTE. When set to false the ratio is the number of members that have any demand allocation at all as a percentage of the total number of members.

Line Manager Count

parameter maxManagers

...