Versions Compared

Key

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

...

The ones locked are the mattermost+system+team level properties, and the one unlocked (Severity) is a property added at the object level.

...

...

Types of properties

We should support the following properties in Playbooks by default.

  • Implicit (these won’t be available as options)

    • Status and Assignee

  • Explicit (these would be available as options)

    • Text

    • SelectMultiselect

    • Multi-select

    • Person

    • Multi-person

    • Link

...

How do properties behave

  • Something created at higher levels will be locked at the lower levels.

  • Lower levels can change an object’s visibility, or decide to turn off “Allow changes to options”.

Menu dropdown for properties

...

Menu dropdown for properties when they are locked

...

Info

When allow new options is turned off at the higher level, users at the lower level can disable them.
If that is turned off, this option does not appear at all.

...

Adding select or multi-select options

...

Clicking any of the values directly would allow users to remote, edit or change the color of the options.

...

Visibility option

  • Visibility: Choose whether the property shows in user profiles. Available options are:

    • Always showAlways hide

      • This hides the property from the run for all users, with the option to expand and see the hidden properties.

      Hide when empty (default)

      • This hides the property when its empty from the profile popovers with the option to expand and see the hidden properties. As soon as the value is filled, this property will be shown by default.

    • Always hide

      • This hides the property behind an accordion from the run for all users, with the option to expand and see the hidden properties.

Any new property that gets created has a Visibility option of: Hide when empty.

...

Thus, the proposition for User profile attributes is to not have this option available.

...

Decisions made by the design team

Something created at higher levels will be locked at the lower levels.

Options can be changed if allow options is turned on.

Visibility can also be changed at all the lower levels and cannot be enforced.

Any changes happening at the lower levels are not cascading back up, rather only down.

Allow lower levels (team) to decide whether “Allow for new options” should be turned off.e=

Assignee field for task update

  • Update assignee field to support groups.

...

Considerations

  • We should have the ability to publish properties from the bottom up as well.

  • Add the ability to reset override.