Versions Compared

Old Version 55

changes.mady.by.user Deborah Scott

Saved on

compared with

New Version Current

changes.mady.by.user Deborah Scott

Saved on

Key

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

Panel
bgColor#f5f5f5
titleColor#ffffff
borderWidth0
titleBGColor#000000
titleJSU for Jira Server/Data Center

This is the documentation for JSU for Jira Server/Data Center. If you are using JSU on Jira Cloud, see our JSU Cloud documentation.

...

In the past, users forgot to change the Epic status in time and it was left as

Status
titleTo Do
. Using JSU this does no more happen.

Update field on all issues related as

The field can be on the issue in transition(within the same issue) or on a related issue, like a subtask, a linked issue, or an issue within an Epic (during the transition on the Epic).

...

See: Post Function Concatenation Operations

Info

***new internal note*** applies only for Jira Service Management (JSM) project issues. For non-JSM projects, the regular comment is updated with the field value you define for ***new internal note***.

Cascading Select fields

For Cascading Select fields, you can either use the value of the option you would like to set, or its ID. In either case, there is no need to specify the parent option. For example:

...

If you are using the Update any Issue Field post function in the Create transition, you must put it after the "Creates the issue originally." but before the "Re-index an issue to keep indexes in sync with the database." post function. Depending on the field type, you must add the Store Issue post function after the Update Any Issue Field.

Expand
titleExample configuration in the 'Create' transition - Click here to expand...
Example configuration of a post function on the Create transition.

In step 4 the "Store Issue" post function is needed, which you must add manually in the workflow configuration. In our example, we use a Workflow Precondition before the Update any Issue Field post function.

...