Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Bug Fix

Fixed bug with using numbers in a variable name for hierarchy.
Now the variable name cannot consist only of a number, the name must begin with a letter.
resolved an error with unavailability to Edit some Hierarchies

Example:

12345 -INVALID

a12345 - VALID

In the case of old hierarchies you have an invalid variable that consists only of numbers, please cast it to a valid value otherwise it might throw an error when applying this hierarchy.

New Feature

Added possibility to choose the variable type for a hierarchy between TEXT and USER

Features of variables of type "USER"

1️⃣ One user variable can store one user

2️⃣ Variables of this type can only be used in fields with user selection (reporter, assignee) or in fields with multiple user selection (multi-users picker, people)

⚠️ If you try to use variables of the user type in text fields or fields of the DESCRIPTION or ENVIRONMENT type, then after creating the task, the variable name will be replaced with the user id instead of the user mention.

Here you can find a guide on how to use variables of this type in hierarchies

https://appsdelivered.atlassian.net/wiki/spaces/SITFJC/pages/1926856705/Using+Variables+in+Hierarchy#USER-type
  • No labels