-
New Feature
-
Resolution: Unresolved
-
Minor
-
None
-
Jenkins 2.164.3
JIRA-trigger-plugin 1.0.0
Hi team, I have used JIRA-trigger-plugin, it's a great job. I have some difficulties, I need to get some values from custom field, such as emailAddress.
But when I mapping, it only show the key. I have try 10103.emailAddress, etc, not work.
Could you help me to get this values?
Many thanks
[JENKINS-57630] Support Multi User Picker custom field parameter mapping for email address
Deakey Tan
added a comment - User Picker 
Wisen Tanasa
added a comment - Can you confirm if this is "Multi User Picker" field? It looks like an array to me. If it is, this is currently not supported yet. The currently supported fields can be seen at CustomFieldParameterResolverTest file. We welcome contribution, feel free to submit a pull request to support this feature.
Wisen Tanasa
added a comment - Can you confirm if this is " Multi User Picker" field? It looks like an array to me. If it is, this is currently not supported yet. The currently supported fields can be seen at CustomFieldParameterResolverTest file . We welcome contribution, feel free to submit a pull request to support this feature. Deakey Tan
added a comment - Yes, it's "User Picker (multiple users)". And I have read CustomFieldParameterResolverTest file, confirm that I can't use it now.
Deakey Tan
added a comment - Yes, it's "User Picker (multiple users)". And I have read CustomFieldParameterResolverTest file , confirm that I can't use it now. Wisen Tanasa
added a comment - Thanks for the confirmation. I've converted this issue as a new feature. Feel free to contribute!
For a workaround, you can always use the injected JIRA_ISSUE_KEY environment variable, then hit JIRA and get the information by yourself.
Wisen Tanasa
added a comment - Thanks for the confirmation. I've converted this issue as a new feature. Feel free to contribute!
For a workaround, you can always use the injected JIRA_ISSUE_KEY environment variable, then hit JIRA and get the information by yourself. Deakey Tan
added a comment - Oh, sorry for late, I have resolve this case, use the script to extract the data I need, but I am still looking forward to your new features.
Many thanks
Deakey Tan
added a comment - Oh, sorry for late, I have resolve this case, use the script to extract the data I need, but I am still looking forward to your new features.
Many thanks Wisen Tanasa
added a comment - deakey Can you help share the solution / script that you're using here? It'll be very helpful for the community if they come across a similar requirement.
Wisen Tanasa
added a comment - deakey Can you help share the solution / script that you're using here? It'll be very helpful for the community if they come across a similar requirement. Deakey Tan
added a comment - Yes. In fact, after we set up Custom Field, we will get a result like "aaa, bbb", so I used a shell script to add a mailbox suffix to them.(Because I use Execute Shell to build)
array_user_email=($1) for element in ${array_user_email[@]}; do user_email=$(echo $element"@yourdomain.com"|sed 's/,//g')
Deakey Tan
added a comment - Yes. In fact, after we set up Custom Field , we will get a result like "aaa, bbb", so I used a shell script to add a mailbox suffix to them.(Because I use Execute Shell to build)
array_user_email=($1)
for element in ${array_user_email[@]};
do user_email=$(echo $element "@yourdomain.com" |sed 's/, //g' )
Wisen Tanasa
added a comment - Thanks for sharing them here 
What's the field type for that custom field?