Issue with copy postfunction
The following post function is not working:
The following text parsed in advanced mode will be copied to Parent's Asignados: "+ " + ", " + %{Assignee}
Instead of a list of assignees I get the last assignee only. The history tab shows the last assignee is overwritten all previous instead of being added.
This is version 2.1.26_beta_2
Comments (12)
-
repo owner -
reporter In another workflow I am doing:
The following text parsed in advanced mode will be copied to Ephemeral string 1: "+ " + ", " + %{Assignee} The following text parsed in advanced mode will be copied to Ephemeral string 2: toString(linkedIssues("Proyecto de la auditoria",%{Parent's issue key})) Value of field Ephemeral string 1 in current issue will be copied to field Asignados in every issue returned by the following JQL query: issuekey in (%{Ephemeral string 2})
And it works OK:
-
repo owner I will investigate the reason the comma character doesn't cause any trouble in one case, and it does in the other one.
Anyway, that comma character is not needed at all. I recommend you to use basic parsing mode (simply because it's faster and you don't need the extra features of advanced parsing mode) and remove the comma.
Please, tell me whether doing this change turns the failing assignment work correctly.
-
repo owner I have tried to reproduce the problem JIRA Workflow Toolbox 2.1.21, 2.1.26_beta2 and 2.1.28, on JIRA 6.3.15. In all three versions, the plugin works as expected, i.e., assignee is added to the multi-user picker custom field, without overwriting current content of the field.
I would need a screenshot of your transition's configuration. Only post-functions tab is required. Otherwise, I can't work on an issue I cannot reproduce.
-
reporter Hi Fidel, I still can't get this to work.
I have:
The following text parsed in basic mode will be copied to Parent's Asignados: + %{Assignee}
but it sets Asignados to the assignee from the last subtask executing the postfunction. It should add it to the list instead. This is JIRA 6.1.5
-
repo owner Which type is custom field "Asignados"?
-
reporter User Picker (multiple users)
-
repo owner Adolfo, I have managed to reproduce the problem. It happens only if target field is in parent issue. I was using a field in current issue, and that's why it worked well for me.
I will investigate the problem, and keep you up-to-date.
-
reporter That explain why it works in a paren'ts linked issue (see my comment from 2015-02-3). Thanks.
-
repo owner Hi Adolfo, the bug has been fixed in version 2.1.29_beta_2.
-
reporter Great, thanks for your help.
-
repo owner - changed status to resolved
Released version 2.1.30 fixing the problem.
- Log in to comment
Hi Adolfo,
The text to be parsed you are using is not correct if you intend to add current assignee to a Multi-User Picker custom field called Asignados, in parent issue.
The correct text using advanced parsing mode is:
You can also use basic parsing mode, since you are not using advanced features. To do it you should use the following configuration: