Migration of JWT Parser functions

Workaround

issue.reporter.displayName
//and
issue.watchers.map(u=>u.displayName)

Only possible to access it using an user field, but it is not possible to access to an user with an username, only with the account ID.

Workaround

Text list

let list = ["abc", "def", "ghij", "klmn"];
list.filter(t=> t.length>3)

Number list

let list = [3,2,5,1,6,0];
list.filter(t=> t>3)

Issue list

let current = issue;
let list = issue.links.map(l=>l.linkedIssue);
list.filter(i=>i.priority>=issue.priority)

It won't be possible to use the seed itself, but as long as you have the current issue and the list of issues in variables, it's possible to replicate the functionality.

Workaround

Just like for mathOnIssueList() but using a number list.

Workaround

%{stringToDate(toString(year({issue.created}, RUN_AS_LOCAL)) + "/" +
toString(month({issue.created}, RUN_AS_LOCAL)) + "/" +
toString(getMatchingValue(month({issue.created}, RUN_AS_LOCAL),
[1,2,3,4,5,6,7,8,9,10,11,12], [31, 28, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31])), RUN_AS_LOCAL)}

Workaround

%{sum(toNumberList(jiraExpression("issue.links.map(l=>l.linkedIssue)
.map(e=>e.timeSpent)")))}

It's only possible to do it using our General parser.

Workaround

let list = issue.links.map(l=>l.linkedIssue);
list.filter(i=>i.resolution!=null && ["Done", "Resolved"].includes(i.resolution.name))

Workaround

let issues = issue.links.map(l=>l.linkedIssue);
issues.filter(i=>i.issueType.name=="Bug")

Workaround

new Project(10000)

Workaround

There is no direct way of implementing the same behaviour, but we can filter an issue list comparing some of its fields with the Current issue, so we can check if the current issue has the same fields as any other on that issue list, which would mean that it is a clone. For example:

let current = issue;
let list = issue.links.map(l=>l.linkedIssue);
list.some(i=>i.priority==issue.priority && i.summary==issue.summary)

Workaround

let list = issue.links.map(l=>l.linkedIssue);
list.map(i=>i.customfield_10016 * issue.customfield_10017)

It can be done as long as the mathematical calculations are not complex.

Workaorund

issue.reporter.properties.get("key")

This should work, but it is not working for me.

Workaorund

issue.reporter.displayName
//and
issue.watchers.map(u=>u.displayName)

Only possible to access it using an user field, but it is not possible to access to an user with an username, only with the account ID.

It's not really necessary a workaround, because, for example, if the HTML escapes are in the description and in the summary, then we can just do the following:

issue.summary
//or
issue.description.plainText //Because it's rich text

Workaround

%{union(linkedIssues("is blocked by", linkedIssues("is blocked by")), linkedIssues("is blocked by"))}

Using our General parser we can access the current issue's linked issues and theirs linked issues.

Workaround

Since to convert string to date time values the string needs to be written in the ISO 8601 format, the time zones will always be just like it is explained here. With this in mind, a workaround can be build if needed using our parser function getMatchingValue().