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

Compare with Current View Page History

« Previous Version 16 Next »

JWT project properties are key-value pairs added to a project description.

The main goal of the properties is to provide project metadata, which can be referenced and used in multiple features of JWT. The main use cases are:

Format of JWT project properties

A JWT project property can be added to any project description in the following format:

{propertyKey=propertyValue}

The screenshot shows an example with 5 JWT project properties:

Property keyProperty valuePotential use case
codeReviewcompulsoryCould be used to enforce certain parts of the workflow related to code reviews using Condition on JWT project property or Validation of JWT project property.
maxResponseTime30Could be used to set individual SLA times per project. These could be used in combination with JWT JQL functions to set up filter subscription or to automatically update an issue priority using an Update field action.
technologyjavaCould be used in many JWT functions or parser expressions using the Advanced text mode.
databaseoracleCould be used in many JWT functions or parser expressions using the Advanced text mode.
stageURLhttps://stage/myappCould be used in many JWT functions or parser expressions using the Advanced text mode.

Main use cases

Customizing workflow behavior depending on projects

Project properties were initially aimed at customizing your workflow behavior depending on project features (metadata added to projects in the form of project properties).

For example you can use project properties to:

  • Enable/disable transitions depending on project property values.
  • Set project customized values for timelines (dates), costs, weights, or any other date or numerical values used in your workflows. Can also be used for implementing non-numerical or non-date attributes.
  • Set priorities among projects, that may be inherited by issues, for example by using priority adjustment tables.
  • Provide project related metadata that may be used by the workflow post functions to compose project customized dynamic text, setting custom or virtual fields with project customized values, etc, e.g., customer information, servers URLs, etc.

Workflow features based on JWT project properties

Conditions and Validators

Post functions

Logical expressions

JWT project properties can be referenced and validated when writing a logical expression in the Logical mode (e.g in the conditional execution parameter of post functions).

Enhancing JQL search capability by project attributes

You can ask for the value of project properties in your JQL queries, by using 3 JQL functions provided by Jira Workflow Toolbox:

  • projectsWhereTextProperty( project_property, operator, string_literal | regular_expression )
  • projectsWhereNumberProperty( project_property, operator, numeric_literal )
  • projectsWhereDateProperty( project_property, operator, date_literal )

You can use it, among other things, to extend the Jira native Project Category concept, by creating several project classifications by using Project Properties.

Setting default assignee for a project role

One of the two ways available in post-function "Assign to project role" for setting default assignee for a project role uses Project Properties with a certain format.

Available functions

Example

Setting user "feynman" as default assignee for project role "Developers", with internal identifier 10100. As you can be seen in the picture, you can use the name of the project role, or the internal identifier as the project property name. The second option has the de advantage that it's immune to project role renaming. 


If you still have questions, feel free to refer to our support team.