[JIRA] (JENKINS-38797) Resolve Jira customfields from within the parameter mapping

5 views
Skip to first unread message

wisen@ceilfors.com (JIRA)

unread,
Oct 6, 2016, 3:34:01 PM10/6/16
to jenkinsc...@googlegroups.com
Wisen Tanasa updated an issue
 
Jenkins / New Feature JENKINS-38797
Resolve Jira customfields from within the parameter mapping
Change By: Wisen Tanasa
Summary: Resolve Jira customefields customfields from within the parameter mapping
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
Atlassian logo

mtozzi@facilitylive.com (JIRA)

unread,
Feb 10, 2017, 4:49:03 AM2/10/17
to jenkinsc...@googlegroups.com
Marco Tozzi commented on New Feature JENKINS-38797
 
Re: Resolve Jira customfields from within the parameter mapping

Hi Wisen Tanasa,
I use the jira-trigger-plugin in my company and I found it very useful, the possibility to map also the customfields is important for us and I would like to understand if the new feature is in plan in next new version of te plugin and in the case which are the roadmap ?

Thanks for your collaboration,
Marco.

wisen@ceilfors.com (JIRA)

unread,
Feb 10, 2017, 2:38:02 PM2/10/17
to jenkinsc...@googlegroups.com

Thank you Marco Tozzi, I'm glad it's been helpful.

I do not have a roadmap for this plugin, features are added on my spare time and when there are enough demand. I'm currently occupied on other projects and would probably come back to this plugin in 1-2 months for new features. Meanwhile waiting, here are some workaround that you can do:

  1. Enable jira-trigger-plugin in your job
  2. The plugin will inject JIRA_ISSUE_KEY environment variable
  3. Make use of the JIRA_ISSUE_KEY environment variable to hit JIRA REST API
  4. Parse the JSON response back and get the value that you want

You can always file a pull request too of course.

mtozzi@facilitylive.com (JIRA)

unread,
Feb 13, 2017, 4:48:01 AM2/13/17
to jenkinsc...@googlegroups.com

Thanks Wisen Tanasa for you comment,
I will use your suggestion for retrieve the custom fields value .

I hope to see in the next future your updating about this new feature .

Thanks,
Marco.

wisen@ceilfors.com (JIRA)

unread,
Mar 11, 2017, 3:52:01 PM3/11/17
to jenkinsc...@googlegroups.com

Another workaround without hitting JIRA REST API, you can resolve the custom property by entering the following value in the Issue attribute path:

fields.find { it.id == "customfield_12345"}.value

Of course, you should replace customfield_12345 with the custom field ID that you have.
This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)
Atlassian logo

wisen@ceilfors.com (JIRA)

unread,
Mar 11, 2017, 3:53:10 PM3/11/17
to jenkinsc...@googlegroups.com
Wisen Tanasa edited a comment on New Feature JENKINS-38797
Another workaround without hitting JIRA REST API, you can resolve the custom property by entering the following value in the _Issue attribute path_:
{code:java}
fields.find { it.id == "customfield_12345"}.value{code}

Of course, you should replace customfield_12345 with the custom field ID that you have.

vmadaan@adt.com (JIRA)

unread,
Sep 10, 2019, 12:54:03 PM9/10/19
to jenkinsc...@googlegroups.com

Hello

 

I am having similar issue. My build is not getting triggered but in the even logs on jenkins i see
Sep 10, 2019 11:48:54 AM FINE org.codehaus.groovy.runtime.callsite.PojoMetaMethodSite$PojoCachedMethodSiteNoUnwrap invoke
Received Webhook callback from changelog. Event type: jira:issue_updated
This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)
Atlassian logo

wisen@ceilfors.com (JIRA)

unread,
Sep 10, 2019, 3:10:02 PM9/10/19
to jenkinsc...@googlegroups.com

Vipul Madaan I'm not sure if your issue is related to this ticket, please do raise another ticket.
Reply all
Reply to author
Forward
0 new messages