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

Compare with Current View Page History

« Previous Version 43 Next »

On this page

Those fields acquire numeric codes from 0 to 9999.

How to search the table content faster

By adding filters to the table you can find your field codes/names faster! Have a look at the video below:

sample screencast

Error rendering macro 'multimedia'

com.atlassian.renderer.v2.macro.MacroException: Cannot find attachment 'pagePropertiesReport_search.mp4'

Field code nameField code server (context "issue")Field code server (context "parent")Map
Ephemeral number 1

%{issue.temporaryNumber1}

00058

%{parent.temporaryNumber1}

00115

(error)
Ephemeral number 2

%{issue.temporaryNumber2}

00059

%{parent.temporaryNumber2}

00116

(error)
Ephemeral number 3

%{issue.temporaryNumber3}

00060

%{parent.temporaryNumber3}

00117

(error)
Ephemeral number 4

%{issue.temporaryNumber4}

00064

%{parent.temporaryNumber4}

00118

(error)
Ephemeral number 5

%{issue.temporaryNumber5}

00065

%{parent.temporaryNumber5}

00119

(error)
Ephemeral string 1

%{issue.temporaryText1}

00061

%{parent.temporaryText1}

00120

(error)
Ephemeral string 2

%{issue.temporaryText2}

00062

%{parent.temporaryText2}

00121

(error)
Ephemeral string 3

%{issue.temporaryText3}

00063

%{parent.temporaryText3}

00122

(error)
Ephemeral string 4

%{issue.temporaryText4}

00066

%{parent.temporaryText4}

00123

(error)
Ephemeral string 5

%{issue.temporaryText5}

00067

%{parent.temporaryText5}

00124

(error)

The following fields are generated by certain apps once they are installed in your Jira instance. Their field code is stored in the internal code, and it becomes available to be used once you install the plugin which belongs to.

You need to be a Jira administrator to install apps!

Field code nameThird-party pluginField code serverField code cloudMap
Tempo Account KeyTempo Timesheets

%{issue.tempoAccountKey}

00182

%{parent.tempoAccountKey}

00181

(error)(error)
Tempo Account NameTempo Timesheets

%{issue.tempoAccountName}

00180

%{parent.tempoAccountName}

00183

(error)(error)
Team NameAdvanced Roadmaps

%{issue.teamName}

00224

%{parent.teamName}

00225

(error)(error)
Customer request channelJira Software Management

%{issue.customerRequestChannel}

00196

%{parent.customerRequestChannel}

00197

(error)(error)
Customer request type name

Jira Software Management

%{issue.customerRequestTypeName}

00178

%{parent.customerRequestTypeName}

00179

(error)(error)

The following fields are considered multi-valued fields:

  • Component/s
  • Component/s leads
  • Affects version/s
  • Fix version/s
  • Labels
  • Attachments
  • Watcher
  • Available transitions
  • Available target statuses
  • Recent attachments
  • Custom fields
    • Select List (Multiple choice)
    • Checkboxes
    • Labels
    • User picker (multiple users)
    • Group picker (multiple groups)
    • Version picker (multiple versions)
  • Issue Picker

The special thing about these fields is that they can be treated as lists when we have an expression that contains a logical operator.

For example, the following expression would work on server without the need of using the function toStringList(), but with other fields that are not multi-valued, like Summary, we would need to use it. 

%{issue.versions} in %{issue.fixVersions}
  • In case you try to use it as a string parameter in a function, that's not working. In that case you have to wrap in with  toStringList().
  • In case you compare such a field with a list built by "toStringList" where this StrigList is the left-hand operator, it's not working
  • fortunately that's not important for the transpilation as we are only transpiling correct JWT parser expressions

JWT parser always runs on a parsing context. The parsing context consists of 3 lists: issue list, string list and number list. The content of this lists are the elements of the context. There are 3 kind of elements: issues, strings and numbers. Elements in a list are ordered, thus each element in these list has an index associated (0, 1, 2, ...).

The index 0 makes reference to the current issue. The index 1 references the seed.

In Cloud, we don't have available the indexes after 1 (2,3,4...), and for the migration we will only migrate the index 0 from Server .

More details about the parsing context can be found here.

The following context are availble

  • issue
  • parent
  • seed

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