Issue Picker FIeld with Jira Workflow Toolox postfunctions

[Pierre Ibrahim]

Hello,

I am currently using the Issue Picker Field plugin by Codecentric AG, and using the Jira Workflow Toolbox by Decadis plugins. 

I have an issuepicker field defined in the issue picker field plugin, and I can reference the field in JWT postfunctions through Jira Expression only: 

However when I switch to general, I can never get the field to show a value

The field itself does not show up in the "Add field" drop down box, however it's not erroring out when I try to reference it directly.

The goal from doing this is to use the issuesFromJQL() function with the value from that issuepicker field. I couldn't find an equivalent way to do it via Jira Expression.

Any help would be greatly appreciated!

[Sergio García-Consuegra _Decadis AG_ · Accepted solution]

Hi @Pierre Ibrahim ,

My name is Sergio, I'm a member of the support team from Decadis.

The reason why this field doesn't appear it's because at the moment we don't offer  compatibility for that plugin yet.

However, as you mentioned, this field value can be retrieved with the "Jira expression" mode.

So you can achieve your current requirement by combining your issuesFromJQL parser function with our parser function jiraExpression() , which allows you to execute a specific fragment of a Jira expression you introduce as a parameter.

For example, with this General mode expression you can execute a JQL search of the issues that have been selected in your Issue Picker custom field:

%{issuesFromJQL("key = (" + jiraExpression("issue?.customfield_11257") + ")")}
 

We hope you find useful this information. In case you have any other doubt, just let us know and we will gladly assist you.

We would suggest that if you have any doubt regarding Jira Workflow Toolbox for Jira Cloud or any other of our apps you can just open a new request in our customer portal. This will make easier the communication between us.

Best regards,
Sergio

[Pierre Ibrahim]

@Sergio García-Consuegra _Decadis AG_ this works great! Anyway to get a specific field value from that JQL? I tried the fieldValue() function but it doesn't seem to like taking an issuekey

[Sergio García-Consuegra _Decadis AG_]

Hi @Pierre Ibrahim ,

I'm happy to hear the provided solution works as expected!

I was able to make the expression work using the fieldValue() parser function. This is the General expression which I used, and which I already adapted to use your custom field code:

%{fieldValue(%{issue.summary}, issuesFromJQL("key = (" + jiraExpression("issue?.customfield_11257") + ")"))}

In case this expression doesn't work as expected, please let me know. Just attach a screenshot showing how it looks the current expression which you are trying to configure.

Best regards,
Sergio

[Pierre Ibrahim]

This is awesome! Thank you so much Sergio!

[Pierre Ibrahim]

One last question if I may @Sergio García-Consuegra _Decadis AG_ ,

The field I'm trying to copy is a date field, this is the expression right now:

%{fieldValue({issue.cf10508}, issuesFromJQL("key = " + jiraExpression("issue?.customfield_11257")))}

I've tried surrounding the field in a dateToString() like so:

%{fieldValue(%{dateToString({issue.cf10508}, RUN_AS_LOCAL, RUN_AS_LANG)}, issuesFromJQL("key = " + jiraExpression("issue?.customfield_11257")))}

And tried without the %{

%{fieldValue(dateToString({issue.cf10508}, RUN_AS_LOCAL, RUN_AS_LANG), issuesFromJQL("key = " + jiraExpression("issue?.customfield_11257")))} 

But I can't get it to work.

This is what I get in the log if I try to run the first expression (without the dateToString)

Description

customfield_10508: The Live Date - Implementation must be a string customfield_10509: The Contract Expiration Date must be a string customfield_10205: The Live Date must be a string

What am I doing incorrectly?
 

[Pierre Ibrahim]

I was able to figure out the correct syntax, it's:

%{toString(fieldValue(%{issue.cf10508}, issuesFromJQL("key = " + jiraExpression("issue?.customfield_11257"))))}

Thank you again @Sergio García-Consuegra _Decadis AG_ , greatly appreciated! 

[Sergio García-Consuegra _Decadis AG_]

Hi @Pierre Ibrahim ,

I'm happy to hear you were able to make it work as you wanted and that my assistance was helpful!

As mentioned before, if in the future you have any doubt regarding Jira Workflow Toolbox for Jira Cloud or any other of our apps you can just open a new request in our customer portal. This will make easier the communication between us and our team will be there to assist you!

Hope you have a nice rest of the week :) 

[Lucas Knorr]

Hi @Pierre Ibrahim,

I’m with codecentric, the developer of the Issue Picker app. Could you share a bit more about what you’re trying to achieve? If your goal is to perform actions on the selected issues, you can also use the native automation rules, which allow you to iterate over the picked issues and apply actions to them.

[Pierre Ibrahim]

Hi @Lucas Knorr 

Essentially what I'm trying to achieve here is I have a task that has the issue picker field, that task has a transition that spins up a subtask with field values from the issue picker field's values.

I have a post function that copies field values from the issue picker's issue into the task triggering the transition, then I have another post function (in the screenshots above) that is supposed to create a child task with the values retrieved. However I'm finding out that JIRA Cloud does not run post functions sequentially, but more in a "fire and forget" type approach, and what I end up with is a child task with some correct values, and some blank values.

What I though I would do to bypass this is to try to get the issue picker field value directly in the JWT post function (screenshot in main post) to then leverage one of their functions to retrieve the values I need from the issue in the issue picker field.