JQL functions are limited by the job name only
Description
Environment
None
Activity
Show:

Mark Rekveld August 17, 2017 at 6:28 PM
Updated the JobDAO.find(String name)
method to also search the displayName
field.

Mark Rekveld July 13, 2017 at 4:16 PM
The project is currently undergoing some refactoring in preparation for Cloud support, so its hard to provide any EAT.
But feel free to checkout the code and contribute. The code links are on the side panel as well as on the Atlassian Marketplace listing.

Alan Ranciato July 13, 2017 at 12:38 PM
Thanks for the update. Any idea on timing? Is the code open sourced? If so, we might be able to assist.
Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Details
Assignee
Unassigned
UnassignedReporter

Components
Fix versions
Affects versions
Priority
Zoom
Open Zoom
Created July 13, 2017 at 12:19 PM
Updated November 16, 2017 at 8:16 PM
Resolved August 17, 2017 at 6:28 PM
Zoom
Currently all JQL functions use the
JobService.find(String)
method to resolve a JQL job name to an actual job to use that to query for issues related to that job of one of its builds.However then Jenkins branch plans are used, there may be a multitude of jobs that all have the same name, like master or develop. The may apply to folder and pipeline jobs as well.
Users should either be able to provide the
urlName
of a job, or use thedisplayName
that is used throughout the plugin.