Skip to content

Instantly share code, notes, and snippets.

@christiangalsterer
Last active December 16, 2019 20:28
Show Gist options
  • Star 8 You must be signed in to star a gist
  • Fork 4 You must be signed in to fork a gist
  • Save christiangalsterer/53f2a84b5e6b0265dd12 to your computer and use it in GitHub Desktop.
Save christiangalsterer/53f2a84b5e6b0265dd12 to your computer and use it in GitHub Desktop.
Atlassian Jira: Number of issues in a Jira Query Language (JQL) search

Description

A Dashing widget to display the number of issues returned by a Jira Query Language (JQL) search. The number of issues will be displayed using the Numbers widget. This widget is a generalized version of the Atlassian Jira: Number of issues in a Jira filter query widget, which shows the number of issues for saved Jira filter.

Dependencies

The following dependencies are required. Please add them to your dashing gemfile.

gem 'jira-ruby', :require => 'jira'

Run bundle install

Installation

If you want to install the widget manually put the file jira_number_of_issues_in_query.rb file into the /jobs directory.

If you want to install the widget automatically type:

dashing gist 53f2a84b5e6b0265dd12

Usage

1. Adjust Job Configuration

Change the JIRA_PROPS in the jira_number_of_issues_in_query.rb file to the correct URL of your Jira installation, e.g.

JIRA_PROPS = {
  'url' => URI.parse("https://localhost:8080"),
  'username' => 'username',
  'password' => 'password',
  'proxy_address' => nil,
  'proxy_port' => nil
}

Put all the filter names or filter ids in the query_mapping, e.g.:

query_mapping = {
  'query1' => { :query => 'project = "MyProject"' },
  'query2' => { :query => 'filter in ("My Open Items")' }
}

2. Adjust Dashboard Configuration

Add the following widget HTML snippet for each jql filter to your dashboard erb file.

<li data-row="1" data-col="2" data-sizex="1" data-sizey="1">
  <div data-id="query1" data-view="Number" data-title="My Open Items"></div>
</li>

Multiple widgets can be shown on a dashboard by repeating the above snippet and changing data-id along with the filter name specified in the filter_mapping in the jobs/jira_number_of_issues_in_query.rb file.

Preview

Compatibility

The widget was tested with the following Jira versions.

Jira Tested By Verified
5.0.6 Christian Galsterer OK
6.1.7 Christian Galsterer OK

License

The widget is provided unter the Apache License, Version 2.0. You may obtain a copy of the License at (http://www.apache.org/licenses/LICENSE-2.0)

require 'jira'
JIRA_PROPS = {
'url' => URI.parse("https://localhost:8080"),
'username' => 'username',
'password' => 'password',
'proxy_address' => nil,
'proxy_port' => nil
}
# the key of this mapping must be a unique identifier for your jql filter, the according value must be the jql filter id or filter name that is used in Jira
query_mapping = {
'query1' => { :query => 'project = "MyProject"' },
}
jira_options = {
:username => JIRA_PROPS['username'],
:password => JIRA_PROPS['password'],
:context_path => JIRA_PROPS['url'].path,
:site => JIRA_PROPS['url'].scheme + "://" + JIRA_PROPS['url'].host,
:auth_type => :basic,
:ssl_verify_mode => OpenSSL::SSL::VERIFY_NONE,
:use_ssl => JIRA_PROPS['url'].scheme == 'https' ? true : false,
:proxy_address => JIRA_PROPS['proxy_address'],
:proxy_port => JIRA_PROPS['proxy_port']
}
last_issues = Hash.new(0)
query_mapping.each do |query_data_id, query|
SCHEDULER.every '10s', :first_in => 0 do |job|
last_number_issues = last_issues['query_data_id']
client = JIRA::Client.new(jira_options)
current_number_issues = client.Issue.jql(query[:query]).size
last_issues['query_data_id'] = current_number_issues
send_event(query_data_id, { current: current_number_issues, last: last_number_issues})
end
end
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright 2014 Christian Galsterer
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
@karthigb
Copy link

I am having difficulty getting this to work. Jira is running on http://jira:8080.

When I set url => "http://jira:8080", I get a BAD REQUEST exception,

When I set url => "https://jira:8080", I get the exception below.

Little help?

$ dashing start
Thin web server (v1.6.2 codename Doc Brown)
Maximum connections set to 1024
Listening on 0.0.0.0:3030, CTRL+C to stop
scheduler caught exception:
No connection could be made because the target machine actively refused it. - connect(2)
c:/Ruby200/lib/ruby/2.0.0/net/http.rb:878:in initialize' c:/Ruby200/lib/ruby/2.0.0/net/http.rb:878:inopen'
c:/Ruby200/lib/ruby/2.0.0/net/http.rb:878:in block in connect' c:/Ruby200/lib/ruby/2.0.0/timeout.rb:52:intimeout'
c:/Ruby200/lib/ruby/2.0.0/net/http.rb:877:in connect' c:/Ruby200/lib/ruby/2.0.0/net/http.rb:862:indo_start'
c:/Ruby200/lib/ruby/2.0.0/net/http.rb:851:in start' c:/Ruby200/lib/ruby/2.0.0/net/http.rb:1367:inrequest'
c:/Ruby200/lib/ruby/gems/2.0.0/gems/jira-ruby-0.1.10/lib/jira/http_client.rb:25:in make_request' c:/Ruby200/lib/ruby/gems/2.0.0/gems/jira-ruby-0.1.10/lib/jira/request_client.rb:13:inrequest'
c:/Ruby200/lib/ruby/gems/2.0.0/gems/jira-ruby-0.1.10/lib/jira/client.rb:155:in request' c:/Ruby200/lib/ruby/gems/2.0.0/gems/jira-ruby-0.1.10/lib/jira/client.rb:134:inget'
c:/Ruby200/lib/ruby/gems/2.0.0/gems/jira-ruby-0.1.10/lib/jira/resource/issue.rb:50:in jql' c:/Ruby200/lib/ruby/gems/2.0.0/gems/jira-ruby-0.1.10/lib/jira/base_factory.rb:33:inblock (2 levels) in delegate_to_target_class'
c:/repo/dashing/jira_dash/jobs/jira.rb:34:in block (2 levels) in <top (required)>' c:/Ruby200/lib/ruby/gems/2.0.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:230:incall'
c:/Ruby200/lib/ruby/gems/2.0.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:230:in trigger_block' c:/Ruby200/lib/ruby/gems/2.0.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.rb:204:inblock in trigger'
c:/Ruby200/lib/ruby/gems/2.0.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/scheduler.rb:430:in call' c:/Ruby200/lib/ruby/gems/2.0.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/scheduler.rb:430:inblock in

@craig
Copy link

craig commented Jul 13, 2014

Hi, JIRA has a maxResults setting of 50 by default, it seems.
It's also way easier to fetch the results like this:

'query1' => { :query => 'project=SECURITY&maxResults=0' },

Which would result in the following URL: https://jira/rest/api/2/search?jql=project=SECURITY&maxResults=0
and return just the number of matching issues in a single string, which is much better than showing all metadata and content of all the tickets!
{"startAt":0,"maxResults":0,"total":3274,"issues":[]}

However,

It gets encoded to https://jira/rest/api/2/search?jql=project%3DSECURITY%26maxResults%3D0
instead of https://jira/rest/api/2/search?jql=project=SECURITY&maxResults=0
So in my webserver logs, I can see this:

x.x.x.x - - [13/Jul/2014:17:21:50 +0200] "GET /rest/api/2/search?jql=project%3DSECURITY%26maxResults%3D0 HTTP/1.1" 400 6541 "-" "Ruby"
x.x.x.x - - [13/Jul/2014:17:22:21 +0200] "GET /rest/api/2/search?jql=project=SECURITY&maxResults=0 HTTP/1.1" 200 865 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:29.0) Gecko/20100101 Firefox/29.0"

Is there any way to fix this? We would just need to get rid of the url encoding.

@cwhd
Copy link

cwhd commented Oct 6, 2014

Correction from above, if you want to install this automatically do this:
dashing install 53f2a84b5e6b0265dd12

@jjlevy
Copy link

jjlevy commented Feb 26, 2015

I have a working instance connected to our Jira instance, but my queries are maxing out at 50 entries. This is most likely due to the Jira page restriction of only showing 50 results at a time. Anyone know of a way to get around this?

@Ishino
Copy link

Ishino commented Jun 25, 2015

I've added the following to get around the 50 limit:

query_options = {
  :fields => [],
  :start_at => 0,
  :max_results => 1000
}
current_number_issues = client.Issue.jql(query[:query], query_options).size

I hope it helps

http://stackoverflow.com/questions/25135622/jira-ruby-gem-limiting-number-of-returned-isues

@patilkunal2563
Copy link

I am trying to run dashboard using dashing start, my JIRA server is at localhost:8080 (127.0.0.1:8080) and when I enter dashing start command I get below error,

scheduler caught exception:
No connection could be made because the target machine actively refused it. - connect(2) for "localhost" port 443
C:/Ruby22-x64/lib/ruby/2.2.0/net/http.rb:879:in initialize' C:/Ruby22-x64/lib/ruby/2.2.0/net/http.rb:879:inopen'
C:/Ruby22-x64/lib/ruby/2.2.0/net/http.rb:879:in block in connect' C:/Ruby22-x64/lib/ruby/2.2.0/timeout.rb:73:intimeout'
C:/Ruby22-x64/lib/ruby/2.2.0/net/http.rb:878:in connect' C:/Ruby22-x64/lib/ruby/2.2.0/net/http.rb:863:indo_start'
C:/Ruby22-x64/lib/ruby/2.2.0/net/http.rb:852:in start' C:/Ruby22-x64/lib/ruby/2.2.0/net/http.rb:1375:inrequest'
C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/jira-ruby-0.1.17/lib/jira/http_client.rb:
25:in make_request' C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/jira-ruby-0.1.17/lib/jira/request_client. rb:14:inrequest'
C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/jira-ruby-0.1.17/lib/jira/client.rb:179:i
n request' C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/jira-ruby-0.1.17/lib/jira/client.rb:158:i nget'
C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/jira-ruby-0.1.17/lib/jira/resource/issue.
rb:63:in jql' C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/jira-ruby-0.1.17/lib/jira/base_factory.rb :33:inblock (2 levels) in delegate_to_target_class'
C:/Users/Kunal.Patil/Desktop/Dashing test/j_i_r_a_dashboard_test_v1/jobs/jira_nu
mber_of_issues_in_filter.rb:39:in block (2 levels) in <top (required)>' C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs. rb:230:incall'
C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs.
rb:230:in trigger_block' C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/jobs. rb:204:inblock in trigger'
C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/sched
uler.rb:430:in call' C:/Ruby22-x64/lib/ruby/gems/2.2.0/gems/rufus-scheduler-2.0.24/lib/rufus/sc/sched uler.rb:430:inblock in trigger_job'

I am trying to solve issue from last 2 hours but I am not able to find any suitable solution.
I will appreciate any help from your end.

Thanks,
Kunal

@rompic
Copy link

rompic commented Nov 5, 2019

if you only want the number of issues use max_results: 0 and remove the .size in https://gist.github.com/christiangalsterer/53f2a84b5e6b0265dd12#file-jira_number_of_issues_in_query-rb-L34

current_number_issues = client.Issue.jql(query[:query]).size

->
current_number_issues = client.Issue.jql(query[:query], max_results:0)

more information here (this feature was added after this gist was created):
https://github.com/sumoheavy/jira-ruby/pull/167/files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment