Versions Compared

Key

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

...

...

...

...

Constraint Types

Min/Max Value

This constrain allows a minimum and maximum value to be set for the input data. The data must fall between these values in order for the user to be allowed to complete the operation. Because of the nature of this constraint only numeric, date, and interval data types may be used with this constraint.

...

...

Supported Types

Sequence

Boolean

Number

Real

String

Date

Date Time

Interval

(error)

(error)

(tick)

(tick)

(error)

(tick)

(tick)

(tick)

Static List

A static list constraint requires the user to select an option from the pre-configured list of values. When entering values in this list you must also set a key. The key should match the key in the database. This will allow the values in Jira to be refreshed when changes are made in the database.

...

Yes? Yes, it is a static list of pairs (key, value) that should have a correspondent in the database - the key. Now, in order for the search to work, the keys should be in the database, but if you plan on also inserting new data, maybe some keys that are not already there, you might have keys that are not in the DB. Searching for them should yield no results, not until you use them to insert something. It’s also a clever way of adding ‘decoration’ to otherwise simplified values/codes in the database.

...

While the key must match, the text is not required to match the values in database.

Supported Types

Sequence

Boolean

Number

Real

String

Date

Date Time

Interval

(error)

(error)

(tick)

(tick)

(tick)

(error)

(error)

(error)

Dynamic List

A dynamic list allows for a script to be used to generate the list. This could allow for different allowed values based on Jira project, parent Epic, user, etc. Aside from SIL scripts, you can use a different table in the same database as a registry to populate here. So if the main table has make_code as a column, and you have another table with [make_code, make_details] you could use the second table to populate this constraint.

...

Constraints by Data Type

...

Type

...

Min/Max Val

...

Static List

...

Dynamic List

...

Sequence

...

(error)

...

(error)

...

(error)

...

Boolean

...

(error)

...

(error)

...

(error)

...

Number

...

(tick)

...

(tick)

...

(error)

...

Real

...

(tick)

...

(tick)

...

(error)

...

String

...

(error)

...

(tick)

...

(tick)

...

Date

...

(tick)

...

(error)

...

(error)

...

Date Time

...

(tick)

...

(error)

...

(error)

...

Interval

...

(tick)

...

(error)

...

Supported Types